Hello Feu, Denys and me working on pretty big setup of Icinga2, in this setup we have several different teams(Operations/Devs/etc.), each team have their own Icinga2 cluster, we need to monitor clusters of Icinga2 that we provide to the teams + our own infra.
Icinga2 doesn’t have client/server application package structure, and the same demon stands as a server and client at the same time. Currently we are trying to start additional demon as a client for Team Icinga2 clusters.
In this schema we don’t have an interest to monitor Team N agents (see picture attached), but we need to ensure that Icinga2 servers we provide to the teams are healthy, also we need some kind of auto-remediation(Event commands) on clusters we provide to provide better high-availability if any services will go down, so passive checks in this case will be not an option for us and we need agent to monitor services and restart them automatically if required.
Regarding multiple-environments we expect that it will allow us to start multiple icinga2 demons on same system or demon will start with 2 different ports:
- First for Icinga2 cluster to process payload from team agents
- Second for our own monitoring needs
Icinga2 objects: ApiListener and IcingaApplication both have an option
environment but it completely unclear for us on how to set it correctly, we’ve tried different configurations for it but didn’t succeeded in that and looking for some assistance.
Hope it will provide you more insights of what we are trying to implement.
Any config examples or recommended steps are highly appreciated.
With best regards,