-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New component: DNS Query receiver #34954
Comments
Can you detail the metrics you would create with this? Names and attributes in particular. |
I don't have strong opinions on this and haven't invested much time in this yet, so I'm open to input. I'd do it similar to telegraf's dns query plugin / the httpcheckreceiver. Here is a first draft: dns_query.duration
attributes
dns_query.status
1 if the check resulted in attributes
For rcode we could also use int type and just stick with the int representation 2 I can put some more effort into this, especially if this it is decided that we want go forward with this proposal becoming a receiver. The format also depends how extensive we want to make this receiver. This is a rather minimalistic version. Footnotes |
The purpose and use-cases of the new component
The DNS query receiver is used to collect latency and error metrics about a DNS server. This receiver doesn't ingest observability data from an external source, but rather repeatedly performs DNS queries itself to produce the desired data.
This proposal is inspired by the existing Telegraf DNS Query Input Plugin
Example configuration for the component
Telemetry data types supported
metrics
Is this a vendor-specific component?
Code Owner(s)
No response
Sponsor (optional)
No response
Additional context
I don't have a code owner or a sponsor. I'm opening this issue to see whether there is interest in general to have such a receiver and if so, to find a sponsor.
There are few similar use cases that come to mind for such a component:
The latter two points are also covered by
httpcheckreceiver
, though the complexity of modern http is much higher compared with traditional DNS.The text was updated successfully, but these errors were encountered: