The documentation is top notch. While I did need to read a lot of it when I first started, it got me set up with a distributed monitoring setup (master, multiple satellites) with almost no issues. And as I've expanded my monitoring setup, anytime I've needed to check how to do something the documentation has at least pointed me in the right direction if not giving me a specific example to follow. Once you have the basic setup in place, adding or removing hosts and services is a breeze. Using templates and apply rules, I can often add a basic host definition and it will add all the necessary services without any other work required. And customizing services on a particular host is also very simple once you have the service definitions set up. There are hundreds of service check definitions provided out of the box, but even that doesn't cover every possible thing. Fortunately adding new service check definitions is very easy and can be done for pretty much anything you can think of. This has allowed me to add monitoring of odd custom things without any difficulty beyond defining what needs to be checked in the first place. I primarily work in a Linux environment, and scripting the configuration of new Icinga agents and adding (or removing) hosts from the configuration is a breeze. This allows me to automate the addition of new servers to the monitoring setup, ensuring that new servers never get forgotten about. There's nothing worse than forgetting to add a new system to monitoring, but Icinga makes it easy to avoid. The web interface is clean and easy to use. The dashboard provides at a glance status of all your hosts and services, and it's easy to drill down into them to see exactly what's going on.
January 22, 2026
HA, despite it's working, its configuration is not so easy, mainly during the migration of master nodes. The configuration of Services and Hosts through Director is not easy to copy into differents environments (aka dev, preprod, prod) in case of several Icinga environment.
January 28, 2026