I have a problem with downtimes. We have systems which are only online for a couple of hours a day. When they come online, they send a message to an HTTP API. This API deletes downtimes set for this system and schedules a downtime in 10 hours in icinga2 via the livestatus interface. If the system got shutdown correct, they send again a message to the HTTP API which sets the system in a downtime. Also the Scheduled downtime works if the system is online for >10 hours. A problem occurs when the Zone is not reachable any more and the scheduled downtime should start: the Zone will get set into the scheduled downtime, also Services applied to the Zone. But the server and its services will not start the scheduled downtime and their services are displayed CRITICAL (when they where CRITICAL before the Zone lost connection) in icingaweb2 and also on the NagVis Map.
The downtime is set as follows:
For me it seems like that this behaviour has something to do with the implicit dependency between the Host and the Zone - when the Zone is not reachable no action for the Host will get triggered.
Is it possible to configure Icinga2 in a way that even though the Zone is DOWN and in a DT that also the scheduled DT for the Hosts and their Services "below" this Zone get triggered?
Thanks for any help in advance,