We use AWS Cloudwatch with some Dasboards. Our entire solution is in AWS. From: Unbound-users <[email protected]> on behalf of Havard Eidnes via Unbound-users <[email protected]> Date: Wednesday, 12 November 2025 at 7:37 am To: [email protected] <[email protected]> Cc: [email protected] <[email protected]> Subject: Re: Monitoring unbound?
> Hi! > we are using collectd and graphite for unbound and other metrics > > In the case of unbound we have an old perl wrapper around > "unbound-control stats_noreset" OK. Allow me to follow a tangent, and get up to ride a hobby horse of mine... Our unbound.conf has # don't zero stats on read(!) statistics-cumulative: yes It is beyond me why anyone would have it any other way. What if you wanted to have two distinct monitoring setups looking at the same unbound instance? A counter is a counter! Maybe I'm too much influenced by dealing with SNMP in other parts of my work (but I hope not). Regards, - Håvard
