Expose probe_dns_duration_seconds metric #662
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This follows the same pattern as probe_http_duration_seconds and probe_icmp_duration_seconds: it captures the time it takes to perform the actual request, excluding the time it takes to set up things. probe_duration_seconds includes the time to perform the request as well as all the time it takes to set it up. probe_dns_lookup_time_seconds refers to the time it takes to resolve the target's address, so it doesn't capture the time it takes to make one request for that target. Signed-off-by: Marcelo E. Magallon <[email protected]>
mem
added a commit
to grafana/synthetic-monitoring-agent
that referenced
this pull request
Jul 9, 2020
The forked version of blackbox_exporter exposes a metric called "probe_dns_duration_seconds", which is the time it takes for the DNS check to run, from connection to query and getting results back. Currently SM is relying on probe_dns_lookup_time_seconds, which is the wrong metric for this check, as that is reporting the time it takes to resolve the _target_, which is the DNS *server*. Since we normally pass an IP address as the target, that resolution time is very low (microseconds). The change in blackbox_exporter is in this PR: prometheus/blackbox_exporter#662 Signed-off-by: Marcelo E. Magallon <[email protected]>
prober/dns.go
Outdated
| // we don't use the rtt value returned fom client.Exchange because that | ||
| // includes only the time to exchange messages with the server _after_ | ||
| // the connection is created. We would in principle have three phases: | ||
| // resolve (probe_dns_lookup_time_seconds), connect (request - rtt), |
There was a problem hiding this comment.
To keep things similar to the metric in the other probes, we should break this out into its phases.
There was a problem hiding this comment.
I added the phase label and added the three time measurements, as indicated in the original comment.
Follow probe_http_duration_seconds and add a "phase" label to probe_dns_duration_seconds, which splits the time it takes to complete the check into "resolve" (time to resolve the target name), "connect" (time to connect to the DNS server) and "request" (time to send the query and retrieve the response). Signed-off-by: Marcelo E. Magallon <[email protected]>
|
Thanks! |
mem
added a commit
to grafana/synthetic-monitoring-agent
that referenced
this pull request
Jul 13, 2020
The forked version of blackbox_exporter exposes a metric called "probe_dns_duration_seconds", which is the time it takes for the DNS check to run, from connection to query and getting results back. Currently SM is relying on probe_dns_lookup_time_seconds, which is the wrong metric for this check, as that is reporting the time it takes to resolve the _target_, which is the DNS *server*. Since we normally pass an IP address as the target, that resolution time is very low (microseconds). The change in blackbox_exporter is in this PR: prometheus/blackbox_exporter#662 Signed-off-by: Marcelo E. Magallon <[email protected]>
mem
added a commit
to grafana/synthetic-monitoring-agent
that referenced
this pull request
Jul 13, 2020
The forked version of blackbox_exporter exposes a metric called "probe_dns_duration_seconds", which is the time it takes for the DNS check to run, from connection to query and getting results back. Currently SM is relying on probe_dns_lookup_time_seconds, which is the wrong metric for this check, as that is reporting the time it takes to resolve the _target_, which is the DNS *server*. Since we normally pass an IP address as the target, that resolution time is very low (microseconds). The change in blackbox_exporter is in this PR: prometheus/blackbox_exporter#662 Signed-off-by: Marcelo E. Magallon <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This follows the same pattern as probe_http_duration_seconds and
probe_icmp_duration_seconds: it captures the time it takes to perform
the actual request, excluding the time it takes to set up things.
probe_duration_seconds includes the time to perform the request as well
as all the time it takes to set it up. probe_dns_lookup_time_seconds
refers to the time it takes to resolve the target's address, so it
doesn't capture the time it takes to make one request for that target.
Signed-off-by: Marcelo E. Magallon [email protected]