Master control snap-in: prevent accidental switch flipping
As identified in CheckMK Support ticket SUP-26485, the switches that are part of the Master control snap-in can be flipped without as little as a confirmation
dialog, pending change, or change feedback.
This makes these switches prone to accidental flipping or misclicks, as there is no safeguard and can have catastrophic consequences, for example:
In our scenario where incident creation depends on CheckMK notifications, if the notifications switch is flipped off for any given site, incident creation will be completely disabled for thousands for hosts.
The Master control switch flips are also not part of the audit log, making it difficult to find the account that changed the state of these switches and overall defeating the purpose of audit logging.
Could you please implement a safeguard to avoid accidental switch flipping for such critical components of the core solution?
Comments: 2
Oldest
•
Newest
•
Most likes
•
Fewest likes
-
18 Nov, '25
Mohamed Saleh AdminHi ITProd,
Thanks for posting on our Ideas Portal
With Checkmk 2.5 the changes to Master control are logged in the audit log.
https://checkmk.com/werk/18068 -
28 Nov, '25
Christian FriedrichHello,
Just a note: normally, an alarm is triggered when one of these switches is set to off. To do this, you should install a checkmk agent on the respective backend. Best regards