Thruk VS Naemon

There are also a bunch of web interfaces available such as Thruk

I switched from Nagios to Naemon (a fork of Nagios), the migration is super easy, you don't even have to be nonweldable at all in linux to achieve it, and almost all the config files are compatible. It's also compatible with all the Nagios plugins, but the GUI is way better than the one on Nagios (is called Thruk https://www.thruk.org)

Fast forward 12 years and I have Icinga2 collectors in each datacenter using check_by_ssh to run check_systemd, all front-ended by Thruk. The TIG stack is something on my list of things to look into at some point, but with Dynatrace available to do all the fancy application monitoring, there's no rush.

For alerting for Linux systems, I use Icinga with check_ssh and check_systemd (caveat: distributed primarily on PyPI) with Thruk as the single pane of glass front-end to per-datacenter installations of Icinga.

But there are also other solutions out there that can manage the configs for you such as Thruk or Adagios.

Looks like Nagios Core has the same behavior as Naemon Core: https://github.com/naemon/naemon-core/pull/92

With Statusengine you can add a database backend. I for example only use the Naemon fork of Nagios Core for many years now.

You can also look into Naemon, is a fork of nagios (uses even the same config files, have support for nagios plugins and have a way prettier web interface and dashboard making tools https://www.naemon.io

This open-source project "Nagios Plugins for Linux" provides several binary plugins for monitoring (physical and virtual) Linux hosts with Nagios and Nagios-compatible monitoring systems like Icinga and Naemon.

I switched to Naemon years ago. The communication with the devs is very pleasant.