feat: make probe_duration_seconds match probe_script_duration_seconds
#1593
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For the vast majority of check types,
probe_duration_secondsis reported as the wall time that took to run the prober. This is accurate for the vast majority of cases, but there's one in particular where it is not: k6-backed checks that use external runners.External runners can take a certain time to process a request, which prior to this commit was counted as part of
probe_duration_secondswhile in fact it was not. This commit adds code that parses theprobe_script_duration_secondsmetric returned by k6 runners, and uses that as the duration of the check for both logs andprobe_duration_seconds.Fixes #1508