Schedule Downtime on Satellite > Master

We currently are finalizing a deployment of a HA Icinga setup and are working on automating downtime.

We have multiple satellite zones connecting to a HA master cluster. Configurations are synced down from the master zones to all of our satellites and this seems to be working very well. Check results also propagate up to the masters from the satellites with no issue.

Communication between monitored hosts in our satellite zones to our master zone is limited due to firewall rules.

Our Expectation:

  1. Use icinga2 api to schedule downtime for host/services on satellite.
  2. Downtime is scheduled on Icinga2 satellite
  3. Downtime is reflected on master.

Current Behavior:

  1. Use icinga2 api to schedule downtime for host/services on satellite.
  2. Downtime is scheduled on Icinga2 satellite
  3. Nothing is propagated to master.

There is nothing in the logs to indicate that the downtime ever reaches the master servers.

Is it possible to set downtime on a satellite and have it reflected on the master?

After enabling debug logs I am seeing the following. The downtime is getting to the master but its being discarded:

[2020-08-12 18:14:05 -0400] notice/ApiListener: Discarding 'config update object' message from 'icinga-satellite02.x' (endpoint: 'icinga-satellite02', zone: 'zone1') for object 'server01!total_procs!42334f4f-2ac2-49aa-8abb-20b82f5bfd2e' of type 'Downtime'. Sender is in a child zone.

This makes it seem like the only way to set downtime via the api is with the master directly.

We worked around this limitation by setting up a basic docker nginx proxy on our satellites but I would still like to know if this is intentional behavior.