I am a bit lost configuring Icinga. I read the documentation about distributed monitoring, but I still have one question. Is it possible to configure checks and add agents on the satellites too and to see everything in one IcingaWeb instance, or all hosts and services definition and also the complete hierarchy need to be defined on the master?
Documentation states:
Note : You can only have one so-called “config master” in a zone which stores the configuration in the zones.d directory. Multiple nodes with configuration files in the zones.d directory are not supported .
Does this mean that it is only possible to have one “config master” in the whole setup or it means that in one zone only one node can store the configuration?
All configurations must be completed on the configuration master. The configuration master pushes configuration data to the satellites, and the satellites, in turn, push it to the Icinga2 agents on the endpoints. This means you don’t need to worry about configuring the satellites individually. Configuration should be pushed from the configuration master after deploying Icinga Director or restarting the Icinga2 service if you’re not using Icinga Director.
If you want to apply specific configurations to a particular zone, that can also be done. Keep in mind that if you make changes only on the satellites, the master may overwrite them. While we haven’t tested this ourselves, I am confident that at some point, the master could overwrite any configurations made on the satellites.
Utilize the zone concept and place all specific configurations in their dedicated zones.
Also there is possible to use HA-master setup. But only 1 master has module icinga director.
With configurations, did you mean also checks and services and all other objects configurations, or just hosts? I just want to fully understand the principle on which it works
