Monitoring unbound?

[Havard Eidnes]

Hi,

at work we like monitoring our recursive resolvers.  To that end
we use the collectd package, and our backend is (judging by the
name) graphite (can you tell I don't "own" it myself?), while
presentation is via grafana.

A long time ago I found this external plugin for collectd,

  https://github.com/falzm/collectd-unbound

which was apparently archived in 2021, no longer being developed.
Of course, I have a few patches to it...  This one in turn
depends on the external-to-collectd API presented by

  https://github.com/collectd/go-collectd

All this wrapped up in NetBSD's pkgsrc's patch + build system.

Now, the sad part is that these are (for now) un-committed pkgsrc
packages (yes, I'm looking to fix that), and the build of them
has apparently fallen by the wayside with recent-ish updates --
the latter now apparently depends on the collectd-dev (Debian?)
package, and collectd itself fails to install one of the header
files it wants to include, ref.

   # collectd.org/plugin/fake
   plugin/fake/shutdown.go:6:11: fatal error: plugin.h: No such file or directory
       6 | // #include "plugin.h"
	 |           ^~~~~~~~~~
   compilation terminated.

Now, before I go on to report these issues to the respective
parties (I'll probably do that anyway...), I'd like to ask what
others do in terms of monitoring and visualization of the
monitored values for unbound.  Surely something less rickety has
been put together?  Bonus points for integration with graphite
and grafana.

Best regards,

- Håvard