Werk #752: FIX: compute correct state transitions for notifications

Component	Notifications
Title	FIX: compute correct state transitions for notifications
Date	Apr 4, 2014
Level	Prominent Change
Class	Bug Fix
Compatibility	Compatible - no manual interaction needed
Checkmk versions & editions	1.2.5i3 Not yet released Checkmk Raw (CRE), Checkmk Enterprise (CEE), Checkmk MSP (CME) 1.2.5i3 Not yet released Checkmk Raw (CRE), Checkmk Enterprise (CEE), Checkmk MSP (CME) 1.2.5i3 Not yet released Checkmk Raw (CRE), Checkmk Enterprise (CEE), Checkmk MSP (CME) 1.2.5i3 Not yet released Checkmk Raw (CRE), Checkmk Enterprise (CEE), Checkmk MSP (CME) 1.2.5i3 Not yet released Checkmk Raw (CRE), Checkmk Enterprise (CEE), Checkmk MSP (CME) 1.2.5i3 Not yet released Checkmk Raw (CRE), Checkmk Enterprise (CEE), Checkmk MSP (CME) 1.2.5i3 Not yet released Checkmk Raw (CRE), Checkmk Enterprise (CEE), Checkmk MSP (CME) 1.2.5i3 Not yet released Checkmk Raw (CRE), Checkmk Enterprise (CEE), Checkmk MSP (CME) 1.2.5i3 Checkmk Raw (CRE), Checkmk Enterprise (CEE), Checkmk MSP (CME)

This fixes a problem with the combination of

• Rule based notifications
• Maximum check attempts > 1
• Rule conditions based on the original state of a host or service

When a service got CRIT while having more than one check attempt, the previous (soft) state would be displayed as CRIT, while it is OK in fact. This has been fixed natively when using the Check_MK Micro Core. When using Nagios then during the notification the previous hard state is not always known. In doubt a notification is being sent out rather then omitted.

To the list of all Werks