Hi list, in my current icinga2 setup I’ve got several zones defined with configuration files synced, as described in the documentation for distributed monitoring:
https://www.icinga.com/docs/icinga2/latest/doc/06-distributed-monitoring/#top-down-config-sync for hosts monitored by remote nodes I can see that checks are being handled by the correct source, so that part seems to be working as expected. However, since the network connection to most of these remote zones can at times be unstable (they are located on offshore rigs connected via different wireless technologies) I frequently experience icinga2 reporting that the zone is not connected, via the “cluster-zone” check_command. The problem is that all the remote hosts that these remote icinga nodes are checking are treated as “DOWN” and not “UNREACHEABLE”, which is the desired behaviour, when the zone becomes disconnected. I have defined host dependencies which treats the remote icinga node as a parent for all the hosts they check, but that still doesn’t seem to solve the problem. The problem with the checked hosts being reported as “DOWN” is that an alert is generated for each object, instead of just one alert for the zone being unreachable Is this the correct behaviour? the setup is running on Debian 8.x boxes with icinga 2.7.0-1 with regards, morten _______________________________________________ icinga-users mailing list icinga-users@lists.icinga.org https://lists.icinga.org/mailman/listinfo/icinga-users
