Director deploy changes delayed udpated in Icingaweb2

Environmental Information

Version Infos

icinga2 - The Icinga 2 network monitoring daemon (version: 2.11.2-1)
Icinga Web 2 Version 2.7.3
director 1.7.2

System information:
  Platform: Red Hat Enterprise Linux Server
  Platform version: 7.7 (Maipo)
  Kernel: Linux
  Kernel version: 3.10.0-1062.12.1.el7.x86_64
  Architecture: x86_64


  • Dual Master Setup
  • Orange => Secondary Master
  • Blue => Primary Master

Active Endpoints change from time to time but i read that this is a normal behaviour


Any updates done with the director are delayed or even not updated on the webinterface.
The deployments don’t show any problems and the output of icinga2 deamon -C is fine.

So basically everything configured with the director is displayed with up to 10 minutes delay in icingaweb2.

I have checked multiple logs an can’t find a clue what causes the problem.

Could it simply take that long to distribute the config to the many zones/endpoints in your setup?

I don’t have such a big setup myself, biggest, regarding objects, is

This sometimes takes about a minute to show changes, but this is still only four zones/endpoints.

In this thread:

There is a mentioning that

I probably found more information

The changes are first moved to a zones-stage location.
This seems to be a new feature, from there on it takes very long to move the changes to production (ca 10-15 minutes)

Is there any configuration i´m missing due to the update which needs to be done to increase the speed with which my changes are deplyoed to production?

As you can see the actual “services” are firstly moved to zones-stage.


Provided Image was wrong sorry