Replies: 1 comment
-
Hi Denis, yes we are in fact looking at exactly this on the roadmap. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello,
I am wondering if there are any plans to integrate OpenTelemetry support into your PowerDNS products (such as dnsdist and Recursor). I believe that adding tracing functionality could be extremely useful for debugging complex DNS situations.
For context, here’s an overview of an existing implementation using DNS-collector, your products (dnsdist/recursor), and Tempo from Grafana. In my environment, DNSdist is deployed behind Recursor, and tracing allows me to visualize the path traversal through each components (dnsdist first, then recursor).
As shown, we can use Grafana to visualize relationships between DNS queries and replies, which is particularly helpful in troubleshooting DNS errors.
I would like to point out that while DNS-collector currently handles tracing, it may not be the most efficient approach. It would be significantly more effective if tracing was implemented directly within each product (dnsdist and Recursor) and if they were able to share OpenTelemetry context between them.
I believe this feature could greatly enhance the debugging and monitoring capabilities for DNS infrastructures.
Denis
Beta Was this translation helpful? Give feedback.
All reactions