I've noticed an unusual behavior (at least IMO) concerning escalations.
I was having a problem that as soon as the notifications hit an
escalation, that Nagios would stop notifying. I had last_notification
set to 0, so I couldn't understand why it would stop, instead of
continuing to notify endlessly (like it should when last_notification = 0).
I figured out the problem. I never defined a notification_interval
since you don't need one in an escalation definition. I assumed that
the notifications would just continue at the same notification interval
as defined in the service definition. However, this isn't true. It
appears to default to 0 when there is no notification_interval defined.
And when notification_interval is 0, it means that this should be the
last notification.
To me, logically, if you don't define a notification_interval, it should
keep the one that has already been defined. Defaulting to 0 just kills
the escalation path. This is just a suggestion of something to look at.
Thanks.
-Russell Scibetti
--
Russell Scibetti
Quadrix Solutions, Inc.
http://www.quadrix.com
(732) 235-2335, ext. 7038
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: russell@quadrix.com