Director deploy changes delayed udpated in Icingaweb2

[log1c]

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:

Icinga2 at large scale

Hello community, I was not sure where to put this topic, please move it if it’s under wrong category In this topic i would like to cover several questions: system requirements, possible bottlenecks and benchmarking. Hope this will simplify installation for new users and provide “ready for deploy” cluster schemas and strategy. My main goals are: define benchmarking tools for stress testing of cluster prototype define how scalable Icinga2 is, based on stress tests provide system requirements …

There is a mentioning that

@Solkren

Configuration propagation in the system takes around 5-6 minutes, time calculated from pressing “Deploy” button in Director to getting hosts visualized in Tactical Overview with Pending status