Antwort: How to not send out first service notifications?

[Marc Haber]

On Thu, Oct 19, 2006 at 11:10:56AM +0200, srunschke at abit.de wrote:
> nagios-users-bounces at lists.sourceforge.net schrieb am 19.10.2006 11:04:19:
> > I am monitoring some hosts on the Internet for informational reasons.
> > Since these hosts quite frequently have failed services, I'd like my
> > Nagios to refrain from notifying me if a service is down at the first
> > notification. Subsequent notifications, however, should be sent out.
> > 
> > Is there a way to do this any easier than having no notifications set
> > in the service definition and have a service escalation having the
> > list of contacts that used to be in the service definition?
> 
> If you always only want the 2nd notification, then your approach sounds
> wrong. You shouldn't suppress the first notification always, but instead
> maybe raise the number of consecutive failed checks until you throw
> a hard state, so you do not get too many false warnings.

Actually, it is fine (and desired) for the service to show up in the
web interface as DOWN, and that the history is correctly written.

Greetings
Marc

-- 
-----------------------------------------------------------------------------
Marc Haber         | "I don't trust Computers. They | Mailadresse im Header
Mannheim, Germany  |  lose things."    Winona Ryder | Fon: *49 621 72739834
Nordisch by Nature |  How to make an American Quilt | Fax: *49 621 72739835

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
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