[PATCH] Distinguish between warning and critical notifications

Mark Gius mgius at createspace.com
Tue Nov 24 02:33:15 CET 2009


Mark Gius wrote:
> Hendrik Baecker wrote:
>   
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Am 18.11.09 01:02, schrieb Mark Gius:
>>   
>>     
>>> The patch adds 4 configuration directives to service escalations
>>> definitions:
>>>
>>>    first_warning_notification #
>>>    last_warning_notification #
>>>    first_critical_notification #
>>>    last_critical_notification #
>>>
>>> Behavior is identical to (first|last)_notification, except that they
>>> check against the count of warning/critical notifications instead of the
>>> number of total notifications.
>>>     
>>>       
>> Hi,
>>
>> I really like this but what about unknown state notifications which
>> might be used?
>>   
>>     
> I thought of unknowns right after I sent the patch.  We don't really use 
> them in our deployment, so I wasn't thinking about them during 
> implementation.  It's easy enough to add.
>   
>> What about hostescalations? Would you patch them too?
>>   
>>     
> I was going to question the usefulness of this, but they can be both 
> "down" and "unreachable."  I'll get an updated patch up sometime next week.
>   
And now I'm done.  I've done some sanity checks on this (retention, cgi 
behavior, notification behavior, objects.cache).  I'm running this code 
on our testing instance now, and I'll report back if something awful 
happens.

The Patch adds the following directives to host escalations

    first_down_notification #
    last_down_notification #
    first_unreachable_notification #
    last_unreachable_notification #

Behavior is identical to (first_last)_notification, except that they 
check against the count of down/unreachable notifications instead of the 
total.

I've also added directives to service escalations to handle unknown states

    first_unknown_notification #
    last_unknown_notification #

-Gius
-------------- next part --------------
A non-text attachment was scrubbed...
Name: nagios_escalations.patch
Type: text/x-patch
Size: 45482 bytes
Desc: not available
URL: <https://www.monitoring-lists.org/archive/developers/attachments/20091123/4d77290e/attachment.bin>
-------------- next part --------------
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
-------------- next part --------------
_______________________________________________
Nagios-devel mailing list
Nagios-devel at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-devel


More information about the Developers mailing list