Prometheus metrics about hickory-dns HOT 4 OPEN

Just for reference, I think the way that we should consider integrating this is in two parts. We should probably look at embracing tracing more deeply and then that has its own metrics collectors implemented for promethius.

So, use https://docs.rs/tracing/0.1.37/tracing/ in the libraries and then we could add a configuration to the server binary with a prometheus exporter https://docs.rs/metrics-exporter-prometheus/latest/metrics_exporter_prometheus/, I think those are all the correct things...

from hickory-dns.

This is for a server? Is there anything blocking you from implementing this outside the core trust-dns code?

It's not clear to me that a Prometheus integration should be delivered as part of this project.

from hickory-dns.

Yes, this is for the server. There does not appear to be an internal mechanism to gather metrics within the trust-dns codebase and present those to an external exporter/service (Unbound has an internal statistics feature). Once that's in place, the majority of the work is done and all that's missing is an HTTP endpoint to present the metrics (+ an optional crate feature to enable them).

For C based projects (such as unbound), there's hesitation to natively integrate Prometheus as it requires a web endpoint for the metrics (which of course is a small security nightmare in C). Which is both why unbound has a number of different external exporter projects (in various stages of maintenance) and Go/Rust projects typically just natively integrate (for example: Quickwit).

from hickory-dns.

I think we currently don't have a lot of the infrastructure for this in place, but if you want to contribute, say, something to track statistics in a server, I'd be happy to provide guidance for that.

To me it feels like the server binary that trust-dns delivers is more of a prototype or tech preview and the project is mostly focused on libraries, so for now that's what I'd want to focus on.

from hickory-dns.