I’m investigating the functionality of Icinga to see if it would be a good replacement for our current setup.
The overall architecture I’d be looking at would be a single master (possibly in HA), and a set of satellites - nothing special here. Due to how we’re doing configuration management though, we can’t approach the setup in a top-down fashion; it would instead be very idiomatic for us to store checks on the satellites as plain text files, and use the master purely as an aggregator. In other words, I would want something more like a multi-master + aggregator architecture instead of master and satellites.
I have been reading several threads and docs and I could so far determine the following:
- bottom-up config style is not supported anymore
- thruk could act as a frontend and interface with icinga2, but livestatus may soon be deprecated
- having multiple IDO DBs seems to work, but is discouraged
…and I thus have a few questions:
- is a master able to not just display checks that are stored on satellites, but also communicate back to them (e.g. to issue downtimes)?
- if not, could I use a centralized icingaweb2 to connect to multiple IDO DBs?
- is a multi-master, multi-IDO setup something I should not rely on, because it might be deprecated at some point?