We use cookies to ensure that we give you the best experience on our website.  Visit our Privacy Policy to learn more. If you continue to use this site, we will assume that you are okay with it.

Your choices regarding cookies on this site.
Your preferences have been updated.
In order for the changes to take effect completely please clear your browser cookies and cache. Then reload the page.

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

ComponentNotifications
TitleFIX: compute correct state transitions for notifications
Date2014-04-04 13:22:23
Checkmk EditionCheckmk Raw Edition (CRE)
Checkmk Version1.2.5i3
LevelProminent Change
ClassBug Fix
CompatibilityCompatible - no manual interaction needed

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.