Munin VS Nagios

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.

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

Munin might be something to consider. It has a multitude of options and clients. Including plugins for raspberry's that can report temperatures etc. There is also a lightweight script as a node implementation. I have it running on my openwrt router and my zyxel NAS as well as a bunch of pis

Wow,nice idea go the same idea as u/databender007 ... any numbers on it ? https://munin-monitoring.org/ displays latency numbers for filesystems out the box. Though i don't know if your filesystems stats go with their plugins.

Let's not forget [Munin](https://munin-monitoring.org/) here! Simple, fast, open-source.

There's munin, have you had any experience with that?

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.

Might I suggest Munin then?

I've used this opportunity to look at some recent init files.

Here's one of the first I stumbled upon.

https://github.com/NagiosEnterprises/nagioscore/blob/master/...

It's 288 lines long; the LSB dependency nonsense is 8 lines of that.

Then I looked up one for Postgres;

https://wiki.postgresql.org/wiki/Lsb_conforming_init_script

This one is a whooping 356 lines long, LSB is again about 10 lines long, depending whether you count the header or not.

I don't think the "LSB dependency" argument holds water.

Also, dang it. I told them they needed to update that Core installation doc. You're installing the latest version of Core, right? The one they mention in the doc is like 4.4.6, and 4.4.12 was released today. https://github.com/NagiosEnterprises/nagioscore/releases/tag/nagios-4.4.12

wget -O nagioscore.tar.gz https://github.com/NagiosEnterprises/nagioscore/archive/nagios-4.4.12.tar.gz

As far as i know there is no option to log all executed service checks except the debug log. Probably you are looking for log_service_retries=1 ?