[receiver/httpcheck] Proposal: Add DNS Duration Timing Metric #34987
Labels
enhancement
New feature or request
needs triage
New item requiring triage
receiver/httpcheck
HTTP Check receiver
Component(s)
receiver/httpcheck
Is your feature request related to a problem? Please describe.
I understand that I am able to receive the following metrics from the current httpcheck receiver:
However, these existing metrics do not give us much visibility into the components of the http call and their latencies. I would like to scope this Feature request to just measuring the DNS Portion of the Layer-7 connection. I want to understand how long it takes for DNS host-lookups to respond, and this is particularly important for high-performance api-systems.
Describe the solution you'd like
Add a DNS Lookup duration metric named httpcheck.dnslookup_duration, e.g:
This lookup duration metric only is visible if the httpcheck endpoint is actually a host (fqdn). If the endpoint is an IP Address, then it will not return this value because of course in that particular case, there is no dns lookup being performed. This new field can also be an "optional" metric, such that the user can control whether or not it is enabled.
Describe alternatives you've considered
Not doing this would present no other option but not to know which component of the Layer-7 Call Flow is causing the latency. If it is DNS causing the majority of the latenecy, we are in the dark that this is the case in the current status-quo of this receiver.
Additional context
I have a pull request ready that can do this. I will reference this issue and go from there.
The text was updated successfully, but these errors were encountered: