We currently have two completely seperate Icinga installations in our department, as they are in different networks, checking different hosts for two groups.
We are looking into merging these instances as much as we can, so the configuration and web interface can be managed from a single master instance and sent from this to the satellites and then to the agents, and our existing master and failover servers in the groups become satellites in different zones.
At the moment configuration is edited on the group A and group B masters, and sent down to the agents.
We would need to keep any configuration and checks for group A seperate from group B - as we don’t want group A satellites monitoring group B hosts and vice versa.
Here’s a diagram of the sort of thing we’d like to achieve. Do you think something like this is realistic?
What do you think would be the best way to go about this to minimise the downtime of all the monitoring systems? I’d be really interested in all your opinions whether this setup as shown is a good idea or not!
I know we’d have to re-sign all certificates, which is quite annoying, so if there’s any way to combine the CAs too then I’d definitely be interested to learn Thank you so much!