Hello,
after a lot of time reading the forum, I've created my account. I would really like to have a unified solution to monitor all my hosts and Icinga2 seems perfect for that.
I'm currently experimenting with multiple hierarchies and top-bottom synchronization. I tested a two levels configuration (master-satellite) and it works perfectly. But I'd like to have some insights about node connections for a three levels hierarchy.
I'd like to have three zones (with at least one endpoint for each) :
- global master
---- local master
------- local satellite
In this configuration, I generated all the needed configuration on the "global master": zones and endpoints definitions in its zones.conf and monitoring configurations in its /zones.d folder.
On the "local master", I configured properly the zones.conf file, the same for "local satellite", and activated the accept_config in the api feature for both.
My question is, how should I connect the "local satellite" node so that it interacts with the "local master"? I'd like it to synchronize configuration, and send monitoring data, to the "local master". I tried to connect the "local satellite" node to the "local master" (generate the ticket on "local master", ask it to sign certificates, etc.). But then, the "local master" does not send the "local satellite" its configuration. The "local master" correctly receives its configuration to the master. But how to "ask him" to propagate the "local satellite" configuration to its child node?
Thanks a lot for your help.
after a lot of time reading the forum, I've created my account. I would really like to have a unified solution to monitor all my hosts and Icinga2 seems perfect for that.
I'm currently experimenting with multiple hierarchies and top-bottom synchronization. I tested a two levels configuration (master-satellite) and it works perfectly. But I'd like to have some insights about node connections for a three levels hierarchy.
I'd like to have three zones (with at least one endpoint for each) :
- global master
---- local master
------- local satellite
In this configuration, I generated all the needed configuration on the "global master": zones and endpoints definitions in its zones.conf and monitoring configurations in its /zones.d folder.
On the "local master", I configured properly the zones.conf file, the same for "local satellite", and activated the accept_config in the api feature for both.
My question is, how should I connect the "local satellite" node so that it interacts with the "local master"? I'd like it to synchronize configuration, and send monitoring data, to the "local master". I tried to connect the "local satellite" node to the "local master" (generate the ticket on "local master", ask it to sign certificates, etc.). But then, the "local master" does not send the "local satellite" its configuration. The "local master" correctly receives its configuration to the master. But how to "ask him" to propagate the "local satellite" configuration to its child node?
Thanks a lot for your help.