Module: check_mk
Branch: master
Commit: dc1d705cdb253137ec84176dc69b16be8e5551ad
URL:
http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=dc1d705cdb2531…
Author: Sven Panne <sp(a)mathias-kettner.de>
Date: Thu Dec 21 11:46:40 2017 +0100
5476 FIX Fixed notification numbering of periodic notifications
Previously, non-OK state changes during periodic notifications resetted the
notification number back to 1, in effect restarting escalations. This was
inconsistent with Nagios and is not what one wants: If e.g. a service is in
WARN state for quite some time, and then goes to CRIT, one surely wants to
continue escalation, not reset it.
This problem has been fixed, so problems correctly escalate now.
Change-Id: Ie4a6430619d1cb3548fa63349b4dc27e39d3e303
---
.werks/5476 | 16 ++++++++++++++++
1 file changed, 16 insertions(+)
diff --git a/.werks/5476 b/.werks/5476
new file mode 100644
index 0000000..8346747
--- /dev/null
+++ b/.werks/5476
@@ -0,0 +1,16 @@
+Title: Fixed notification numbering of periodic notifications
+Level: 2
+Component: cmc
+Compatible: incomp
+Edition: cee
+Version: 1.5.0i3
+Date: 1513852752
+Class: fix
+
+Previously, non-OK state changes during periodic notifications resetted the
+notification number back to 1, in effect restarting escalations. This was
+inconsistent with Nagios and is not what one wants: If e.g. a service is in
+WARN state for quite some time, and then goes to CRIT, one surely wants to
+continue escalation, not reset it.
+
+This problem has been fixed, so problems correctly escalate now.