I have created a patch that codifies the behavior mentioned in my
previous email.  The patch does this:

If a recovery *service* escalation request is received:
* If the previous state of the service is listed in the escalation,
allow the recovery escalation
* If the previous state of the service is not listed in the
escalation, do not send the recovery notification

So if you put this in a service escalation definition:

escalation_options u,c,r

You will only get a service escalation if the service state recovers
from an unknown or critical state .. if the state changes to warning
and then ok, no escalation will be sent.

If anyone is interested in this patch, happy to share once we have
used it in our production env for a day or two to make sure it is
stable.  I would also add code for the following before releasing it:
* If recovery is specified and no non-ok states are specified in the
service escalation, allow the escalation.

Regards,
Max

------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time, 
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize  
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
Nagios-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting 
any issue. 
::: Messages without supporting info will risk being sent to /dev/null

Reply via email to