Werk #8100: Fix disabling of notifications when done both via rule and command
| Component | The Checkmk Micro Core | ||
| Title | Fix disabling of notifications when done both via rule and command | ||
| Date | Dec 2, 2014 | ||
| Level | Prominent Change | ||
| Class | Bug Fix | ||
| Compatibility | Compatible - no manual interaction needed | ||
| Checkmk versions & editions |
|
When you have disabled the notifications of a service (or host) via a command and later disabled the notifications of the same service via a rule, then in effect the notification became enabled again! This was due to the internally stored information about which setting has been modified. This has now been fixed. The core now correctly keeps track of which enabling (notifications, active and passive checks) has been modified and which is the new manual setting. The manual setting will override any configuration setting until it is cleared.
Clearing manual settings can be done with the command Clear modified attributes in Multisite (which internall calls CHANGE_HOST_MODATTR or CHANGE_SVC_MODATTR.
Note: The Nagios core behaves different here. Clearing the modified attributes just removes the information that they have been modified - not their actual setting! There is no way to generally remove manual settings here other then manually set all back to their configuration settings and afterwards again issue Clear modified attributes. The CMC decided to not mimick this strange behaviour.