notify contact only once

Richard Mohr rfmohr at osc.edu
Wed Oct 10 17:42:08 CEST 2007


On Mon, 2007-10-08 at 16:13 -0500, Terry wrote:
> On 10/5/07, Aidan Anderson <mail at aidananderson.co.uk> wrote:
> > Terry wrote:
> > >
> > > I have regular contacts set up, me for example.  I want to get
> > > notified every 30 minutes indefinitely if a service is in a hard state
> > > of warning or critical.  However, I want another contact to only get
> > > notified one time when that hard state is achieved.    That's it.
> > > 
[...]
> > I've just posted you another message before seeing this one.  You want
> > to use host or service escalations to achieve this.  I've briefly
> > explained in the previous post but if you need more help, just shout.
> >
> > Aidan
> >
> 
> Thanks for your reply.  It looks like for me to achieve this, I will
> need to create 2 escalations for every service.  One for the single
> notification and the other for standard notifications.  That seems
> like a lot of configuration.

I think you can get by with one escalation.  Configure the service's
contactgroup to include you and the other person.  Then create a service
escalation that kicks in on the second notification and continues
indefinitely. Use the escalation to change the contactgroup to include
only you, and set the notification interval to 30 minutes.

Does that fit your needs?

-- 
Rick Mohr
Systems Developer
Ohio Supercomputer Center


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
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