dnsproxy-config VS Munin

Yes.

You can find the project here, the documentation describes installation alongside or in front of Pi-hole, depending on the use case. If you want secure incoming traffic, a certified FQDN is required. This is left as an exercise for the user (to raise the bar somewhat).

No need for the full AGH stack. You can easily run dnsproxy alongside or in front of Pi-hole.

I have somewhat documented the process of putting up a Do(H|T|Q)/DNScrypt proxy as a standalone service here.

I still need to fix up a couple of permission issues in my documentation, but I have the rough outline of deploying dnsproxy as a standalone simple service here. The last few edits I made to it were getting it to use the yaml syntaxed config file, and trying to make sure a default configuration should Just Work without having to edit it, but you'd still want to.

There's a basic overview here, but I haven't touched it for a while and the documentation may be slightly broken surrounding exec permissions on some files.

It's very possible. You could easily set this up yourself. I do so so myself using dnsproxy, and you could too.

I have an example dnsproxy service here that I use for high availability (one-to-many) distribution and providing encrypted transport.

You might know me as that Unbound guy, or maybe even that dnsproxy guy. Today I would like to make myself known as that Munin guy, and introduce munin-pihole-plugins for Munin Monitoring.

Kinda.

I rediscovered Munin. To my surprise it is written entirely in Perl. I remember Munin from years ago... it still seems healty and maintained and lies ready on your Deb-Repositories. So I followed the Easy Install Guide... which really is easy, but fails to mention that you need to install your own HTTP-Server to serve the HTML-reports.

A bit of background, which may make understanding my choices in this lib easier: Munin is a resource monitoring tool using rrdtool, usually run in a Server/Client Setup. The client accepts plugins which are just executables in a directory. Usually written in a scripting language, but it actually doesn't matter. Data is fetched every 5 minutes, plugins are first run with a config argument to spit out a munin graph config, followed by a run without arguments to present data. To support higher resolutions than just "every 5 minutes", graph config can contain config to tell munin one collects it every second. Then the fetching part needs to run as a daemon, writing a cache somewhere which gets output when munin wants the data.

Munin plugins and management script for monitoring various Pi-hole® statistics.

When you do not have enough power you would get errors because looking up the plots would simply fail. Sounds more that there is one disk which is slower. I had one 2TB external usb which was really slow and the latency of lookups was through the roof. Are you on linux ? Then install munin-monitoring.org it shows latency of the disks out of the box.

what os ? on linux install https://munin-monitoring.org/ it will give you disk latency information.

I'd say give Munin a try.

Munin plugins for monitoring Pi-hole®. Transforms a server into a powerful monitoring platform, as simple as one, two, three, ...four.