munin-pihole-plugins VS elk-hole

My (somewhat ungainly) API-driven Pi-hole plugin example/reference lives here.

You can find the plugin here, the main project repository here, and documentation/wiki here.

Example Pi-hole Munin plugin with telnet and JSON API support by yours truly available here for reference.

I had assumed that I would need to rewrite one or more sections of my munin plugin because I'm monitoring status in one plugin.

If one's self, or anyone else, are interested in something like this, but which attempts to take most of the set-up out of your hands, and focuses more on data presentation than looking pretty, here's a shameless plug for a hobby project of mine, munin-pihole-plugins.

If you'd like to monitor it all in one spot, I'd like to do a little bit of shameless self promotion here and offer this project of mine to assist in automating deploying a distributed full system graphing server. It's intended to run on/alongside Pi-hole, but it can also monitor a Pi-hole instance external to itself.

Again for yourself or anyone else, any queries or concerns regarding the project, what it is or isn't, etc. I'm perfectly happy to address. Bugs, issues, feature requests or feature enhancements should go to the issues page.

More information on installation and usage, including command list, example graph gallery, plugin and script configuration is available at the munin-pihole-plugins project repository.

Should this love interest overlap with a general interest in system/network wide distributed long term monitoring and graphing systems, I'm trying to get eyes on munin-pihole-plugins, and also hopefully some weird edge cases installs for feedback.

Have you looked into deploying elk-hole which forwards logs from pihole to logstash, gets indexed by elastic search and presented by Kibana?