[Nagios-devel] Simple escalations

Support forum for Nagios Core, Nagios Plugins, NCPA, NRPE, NSCA, NDOUtils and more. Engage with the community of users including those using the open source solutions.
Locked
Guest

[Nagios-devel] Simple escalations

Post by Guest »


--Apple-Mail-32--444708897
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
charset=US-ASCII;
delsp=yes;
format=flowed

Hi Ethan,

We've published a patch to Nagios 2.5 where we add a feature for
contacts. You can now set a notification_level and contacts will not
get alerted until the notification number reaches their level.
Details here: http://altinity.blogs.com/dotorg/2006/09/
simple_escalati.html

One problem we've found is that if all contacts fail to get notified
due to their configuration filters, then the notification number is
decremented back to the original. But that means a manager with
notification_level 2 would never get alerted.

Would it make sense for a notification number to still increase if
contact filters fail? If the service filters fail, the notification
number should return back, but if contacts have been defined to
ignore them, then I think the "clock should keep ticking" - ie, the
notification number (the seriousness), keeps increasing.

If so, I think this is the change to notifications.c:

--- notifications.c.original 2006-09-14 17:19:08.918201189 +0100
+++ notifications.c 2006-09-14 17:21:52.813500174 +0100
@@ -213,9 +213,10 @@
svc->notified_on_critical=TRUE;
}
- /* we didn't end up notifying anyone, so
adjust current notification number */
- else
+ /* we didn't end up notifying anyone because
of various contact filters, but the seriousness should keep
increasing */
+ /* else
svc->current_notification_number--;
+ */
}
#ifdef DEBUG4
printf("\tAPPROPRIATE CONTACTS HAVE BEEN NOTIFIED\n");
@@ -1012,9 +1013,10 @@
hst-
>notified_on_unreachable=TRUE;
}
- /* we didn't end up notifying anyone, so
adjust current notification number */
- else
+ /* we didn't end up notifying anyone because
of various contact filters, but the seriousness should keep
increasing */
+ /* else
hst->current_notification_number--;
+ */
}
#ifdef DEBUG4

Ton

http://www.altinity.com
T: +44 (0)870 787 9243
F: +44 (0)845 280 1725
Skype: tonvoon



--Apple-Mail-32--444708897
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
charset=ISO-8859-1

Hi Ethan,We've published a patch to =
Nagios 2.5 where we add a feature for contacts. You can now set a =
notification_level and contacts will not get alerted until the =
notification number reaches their level. Details here:=A0htt=
p://altinity.blogs.com/dotorg/2006/09/simple_escalati.htmlOne problem we've found =
is that if all contacts fail to get notified due to their configuration =
filters, then the notification number is decremented back to the =
original. But that means a manager with notification_level 2 would never =
get alerted.Would it make sense for a =
notification number to still increase if contact filters fail? If the =
service filters fail, the notification number should return back, but if =
contacts have been defined to ignore them, then I think the "clock =
should keep ticking" - ie, the notification number (the seriousness), =
keeps increasing. <SPAN =
class=3D"Apple-style-span" styl

...[email truncated]...


This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]
Locked