Antwort: [PATCH] - 3.0.3: only send out a service recovery escalation if a service is recovering from a non-OK state listed in the escalation or only 'r' is specified as an escalation option

[Max]

On Mon, Jul 20, 2009 at 3:33 AM, <Sascha.Runschke at gfkl.com> wrote:
> I don't think this is feasible, as it changes Nagios core
> functionality. I don't think I'm the only one wanting
> RECOVERY notifications even from WARNING states. If I define
> it that way, I expect it to behave that way.

My patch does that.  If you specify:

define serviceescalation {
   hostgroup_name          nagios_hosts
   contact_groups          admins
   first_notification      1     ; notify right away (1st notification)
   last_notification       0     ; notify until service changes state
   notification_interval   240   ; default to 4 hour re-notify
   escalation_period       24x7
  service_description     .*
   escalation_options      u,w,r
   register                0
}

Then you will get an escalation on warning, unknown, and recovery
escalations when then service returns from unknown OR warning (but in
the above case, *not* critical) to OK

If you put.

define serviceescalation {
   hostgroup_name          nagios_hosts
   contact_groups          admins
   first_notification      1     ; notify right away (1st notification)
   last_notification       0     ; notify until service changes state
   notification_interval   240   ; default to 4 hour re-notify
   escalation_period       24x7
  service_description     .*
   escalation_options      u,r
   register                0
}

You would only receive escalation notifications if the service goes
into an UNKNOWN state or recovers from an unknown state.

Does that clarify it? :)

So from what I hear from you it looks like my patch might fix the very
bug you are mentioning.

- 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