Nagios doesn't stop notifying when it should

Jeff Williams jeffwilliams05 at gmail.com
Wed Nov 23 20:07:15 CET 2005


That makes sense, but I'm confused why I could get away with what I
was doing before and not have it go past 5 notifications. Maybe I was
just lucky or something. I've been using Nagios for a while and have
never needed to set it up this way. Thanks for the response.

Jeff

On 11/23/05, Tedman Eng <teng at dataway.com> wrote:
> Think of service escalations as "in addition to" normal notifications
>
> For notification attempts for which there are no defined escalations, the
> normal contact group is used.  If you want only notification attempts 1-5 to
> be sent, create a contact group called 'none' for the service definition and
> then notify using only escalation definitions.
>
>
> define service
>          contact_groups              none
>
> define serviceescalation
>          first_notification            1
>          last_notification             5
>          contact_groups              ulsysadmins
>
> define serviceescalation
>          first_notification            3
>          last_notification             5
>          contact_groups              oncall,backup
>
>
> -----Original Message-----
> From: Jeff Williams [mailto:jeffwilliams05 at gmail.com]
> Sent: Wednesday, November 23, 2005 8:24 AM
> To: nagios-users at lists.sourceforge.net
> Subject: [Nagios-users] Nagios doesn't stop notifying when it should
>
>
> I know I've submitted this question before and I don't want to spam
> everyone, but someone has to be using escalations that can help me.
> Can someone please help me explain why the first example used to work
> for me and now would not? I am using 2.0b4 (and have been since well
> before having this problem) and now have to use the lines in the
> second example to get notifications to stop after 5.
>
> > define serviceescalation{
> >         host_name                     myserver
> >         service_description        /VAR
> >         first_notification            3
> >         last_notification             5
> >         notification_interval       5
> >         contact_groups              oncall,backup
> > }
> >
> > define service{
> >         use                           generic-service
> >         host_name                 myserver
> >         service_description     /VAR
> >         is_volatile                   0
> >         check_period              24x7
> >         retry_check_interval     1
> >         contact_groups              ulsysadmins
> >         notification_interval       5
> >         notification_period         24x7
> >         notification_options        w,u,c,r
> >         check_command            check_nrpe!check_disk6
> > }
> >
> > What this used to do is notify 'ulsysadmins' for the first two
> > notifications, then escalate to 'oncall' and 'backup' for the third
> > through fifth notifications. Right now it does that, but then for the
> > sixth through infinite notification, it goes back to notifying
> > ulsysadmins. I thought this was enough to tell it to stop at 5
> > notifications. It used to be, but now I need to change the escalation
> > to:
> >
> > define serviceescalation{
> >         host_name                     myserver
> >         service_description        /VAR
> >         first_notification            3
> >         last_notification             4
> >         notification_interval       5
> >         contact_groups              oncall,backup
> > }
> >
> > define serviceescalation{
> >         host_name                     myserver
> >         service_description        /VAR
> >         first_notification            5
> >         last_notification             5
> >         notification_interval       0
> >         contact_groups              oncall,backup
> > }
>
> Thanks.
>
> Jeff Williams
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://ads.osdn.com/?ad_idv37&alloc_id865&op=click
> _______________________________________________
> 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
>


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id865&op=click
_______________________________________________
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





More information about the Users mailing list