[Nagios-devel] Q: Service Escalation Recovery Notifications.

[Paul M. Dubuc]

I should have mentioned that whether this works depends on who the default, 
non-escalated, contacts are for the host or service.  In your case, since you 
have last_notification set to 3, those contacts in your escalation will not 
get a recovery notification that is numbered 5 or greater unless they also 
happen to be the default contact for the host or service, which will get the 
problem notification number 4 and all non-escalated notifications.  If you 
escalate a notification to a contact that is not assigned as a regular contact 
for the host or service, those contacts don't get the recovery notification 
(unless they also got the previous problem notification) even if you set up a 
separate escalation for the recovery notification that specifies all previous 
contacts.

Patrik Båt wrote:
> Are you sure about that?
>
> The documentation says:
> "If, after three problem notifications, a recovery notification is sent
> out for the service, who gets notified? The recovery is actually the
> fourth notification that gets sent out. However, the escalation code is
> smart enough to realize that only those people who were notified about
> the problem on the third notification should be notified about the
> recovery. In this case, the nt-admins and managers contact groups would
> be notified of the recovery."
>
> On Wed, 2011-05-25 at 13:56 -0400, Paul M. Dubuc wrote:
>> This works as long as the problem doesn't last longer than 3 notification
>> intervals.  Recovery notifications that are numbered higher than 4 won't be sent.
>>
>> Patrik Båt wrote:
>> >  # SMS
>> >  define serviceescalation {
>> >           host_name *
>> >           service_description *
>> >           first_notification 2
>> >           last_notification 3
>> >           notification_interval 0
>> >           contacts oncall
>> >  	}
>> >
>> >  define hostescalation {
>> >           host_name *
>> >           first_notification 2
>> >           last_notification 3
>> >           notification_interval 0
>> >           contacts oncall
>> >  	}
>> >
>> >  # MAIL
>> >
>> >  define serviceescalation {
>> >           host_name *
>> >           service_description *
>> >           first_notification 1
>> >           last_notification 1
>> >           notification_interval 10
>> >           contacts sysadmin.reports
>> >  	}
>> >
>> >  define hostescalation {
>> >           host_name *
>> >           first_notification 1
>> >           last_notification 1
>> >           notification_interval 10
>> >           contacts sysadmin.reports
>> >  	}
>> >
>> >  # Recovery
>> >
>> >  define serviceescalation {
>> >           host_name *
>> >           service_description *
>> >           first_notification 2
>> >           last_notification 3
>> >           notification_interval 0
>> >           contacts sysadmin.reports
>> >           escalation_options r
>> >  }
>> >
>> >  define hostescalation {
>> >           host_name *
>> >           first_notification 2
>> >           last_notification 3
>> >           notification_interval 0
>> >           contacts sysadmin.reports
>> >           escalation_options r
>> >
>> >
>> >  This is working for me, to notify both via sms and email. eg 2 contacts.
>> >
>> >
>> >
>> >  On Fri, 2011-05-20 at 22:22 +0200, Andreas Ericsson wrote:
>> >>  On 05/20/2011 06:05 PM, Max Schubert wrote:
>> >>>  Hi,
>> >>>
>> >>>  On Thu, May 19, 2011 at 10:10 AM, Andreas Ericsson<ae at op5.se  <mailto:ae at op5.se>>    wrote:
>> >>>>  On 05/19/2011 03:32 PM, Paul M. Dubuc wrote:
>> >>>>>  OK, but wouldn't it be nice if all contacts who got an error notification were
>> >>>>>  able to get the recovery message instead of just the one last notified?  Is
>> >>>>>  there any way to do that?  Setting up an explicit serviceescalation for
>> >>>>>  recovery notifications doesn't seem to work.
>> >>>>>
>> >>>>
>> >>>>  Max Schubert is working on a patch that does something similar to that.
>> >>>>  If he doesn't complete it, I might take a look at adding it myself.
>> >>>
>> >>>  I will send out my partial patch to the list sometime today along with
>> >>>  an explanation of my thinking / approach for it - feel free to use it
>> >>>  or discard it as you see fit :)!
>> >>>
>> >>
>> >>  Rest assured, I will ;)
>> >>
>> >>  Our customers have raised voices about simplifying the notification
>> >>  logic though. This discussion actually spawned that voice-raising,
>> >>  which is nice. Either way, it might be that I end up either taking
>> >>  your patch or implementing the"everyone who gets problem notifications
>> >>  also get recovery notifications".
>> >>



------------------------------------------------------------------------------
vRanger cuts backup time in half-while increasing security.
With the market-leading solution for virtual backup and recovery, 
you get blazing-fast, flexible, and affordable data protection.
Download your free trial now. 
http://p.sf.net/sfu/quest-d2dcopy1
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
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