munin-pihole-plugins VS Netdata

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.

netdata.cloud — Netdata is an open-source tool to collect real-time metrics. It's a growing product and can also be found on GitHub!

Netdata is designed with efficiency, scalability, and flexibility in mind, aiming to address most of the challenges associated with both open-source tools and commercial SaaS offerings.

Monitoring = netdata on each RPi https://www.netdata.cloud/ binded to the vpn interface being scraped into a prometeus thaons https://thanos.io/ setup with grafana to give management the Green all is good screens (very important).

We run netdata to have a bit of insight into whats happening on the 10+ dedicated servers in Falkenstein. So far we have seen a 1hour_ecc_memory_correctable about once a month. Suddenly we get 1hour_ecc_memory_correctable like every day from different servers. Any ideas why that could be happening?

Documentation and source code of this plugin: https://github.com/netdata/netdata/tree/master/collectors/systemd-journal.plugin

Home Page and source code: https://github.com/netdata/netdata

I started the discussion, and offered a solution too:

https://github.com/netdata/netdata/discussions/16136

hey - I work on ML at Netdata (disclaimer).

We have a big PR open and under review at moment that brings in a lot more logs capabilities: https://github.com/netdata/netdata/pull/13291

We also have some specific logs collectors too - i think in here might be best place to look around at the moment, should take you to the logs part of the integrations section in our demo space (no login needed, sorry for the long horrible url, we adding this section to our docs soon but at moment only lives in the app)

https://app.netdata.cloud/spaces/netdata-demo/rooms/all-node...