Open log1-c opened 1 year ago
Where are these checks executed, are they running on the master or some satellite or agent? Also, are you using any HA zones?
The checks are running one two satellite nodes belonging to one satellite zone.
Looks like that flag is only synced within a zone but not to any child zones, so that change stays within the master zone.
We could stop processing checks from below nodes as long as they're disabled. 🙈
But jokes aside, IW2 actually just updates an attribute of a config object. And that runtime change is just synced inside the zone as usual. As long as not all Icinga 2 versions in a cluster forward such specific attribute updates below, we can only consider the option I described in the above paragraph. As a bridge technology.
We could stop processing checks from below nodes as long as they're disabled. 🙈
I don't think you meant nothing else, but the config changes for the other buttons, especially the Event Handlers, should also be distributed to the child zones. We had to learn this the hard way that event handlers are not disabled globally by toggling the switch in IW2.
Is there another option to "globally" disable host/ service checks and eventhandlers without curl'ing the endpoints in the child zone?
💡 You could try putting the IcingaApplication in a global zone, maybe it will broadcast the updates then. But I don't know whether it works.
Describe the bug
When using the feature command switches under /icingaweb2/health#!/icingaweb2/icingadb/health to disable host or service checks, I would expect them to stop completely. But they are still being executed
To Reproduce
Provide a link to a live example, or an unambiguous set of steps to reproduce this bug. Include configuration, logs, etc. to reproduce, if relevant.
Expected behavior
No checks are executed.
Your Environment
Include as many relevant details about the environment you experienced the problem in