You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have the problem that when the config sync is running, all API requests against the master are unsuccessful. The config sync takes atm about 2 minutes.
If an icinga check in powershell runs during this time window, which has to execute API requests against the master, this will result in an error.
First question:
Is there a way to query via API whether a config sync is currently running or not? -> If we could query whether a config sync is running or not, we could adapt the icinga powershell scripts accordingly. That would help us enormously.
Second question:
Is it possible to trigger a pre and post script before/after the config sync?
We now have over 2000 hosts and over 43000 checks, I'm afraid that the config sync will "at some point" take 10 minutes or more and that we'll create "wild" incidents during this time. How do you generally handle the config sync in "large" environments?
The text was updated successfully, but these errors were encountered:
We have the problem that when the config sync is running, all API requests against the master are unsuccessful. The config sync takes atm about 2 minutes.
If an icinga check in powershell runs during this time window, which has to execute API requests against the master, this will result in an error.
First question:
Is there a way to query via API whether a config sync is currently running or not? -> If we could query whether a config sync is running or not, we could adapt the icinga powershell scripts accordingly. That would help us enormously.
Second question:
Is it possible to trigger a pre and post script before/after the config sync?
We now have over 2000 hosts and over 43000 checks, I'm afraid that the config sync will "at some point" take 10 minutes or more and that we'll create "wild" incidents during this time. How do you generally handle the config sync in "large" environments?
The text was updated successfully, but these errors were encountered: