Icinga
Update 2023: The notes below were last updated in 2017, for what is now quite an old version of Icinga, therefore I have created a new page which discusses setting up Icinga 2.13.6 in a Master-Satellite-Agent configuration.
I like Icinga as a monitoring system. It's a spinoff from the Nagios project, and does (in my opinion) a really good job where you want a hierarchical monitoring system for multiple customers (or maybe multiple departments) who shouldn't see the monitoring for each other's machines:
- I have a Master monitoring system where I do all the configuration, and I can see all machines in Icingaweb2
- Each of my customers has a "satellite" monitoring system, which receives its configuration from my Master server, and shows the customer their own machines in the local copy of Icingaweb2, but has no visibility of the other customers' systems
- Each customer system does its own monitoring, so even if network connectivity is lost between the customer server and my Master server, the customer's monitoring is not affected, and events are later propagated back to the Master when it becomes available again
- A note about Icinga2 Zones
- Adding a new node to an Icinga2 setup
- Moving an installed node from one machine to another
- Adding a useful menu entry to Icingaweb2 for an overview of your machines
- Setting up certificates for a distributed Icinga2 setup, when the Master node can contact satellites, but not vice versa (for example, you want to run the Master node behind a NAT router)
- Performing Icinga2 checks over SSH (eg: when you can't install Icinga itself on the node to be monitored)
- I would dearly like to write about integrating Nagvis with Icinga2, but unfortunately I don't know how to do this yet
Go up
Return to main index.