Event handlers

[Dan Hopkins]

> -----Original Message-----
> From: Chris Wilson [mailto:chris at aidworld.org]
> Sent: 23 March 2005 18:23
> To: Nagios Users
> Subject: [Nagios-users] Event handlers
> 
> 
> Hi all,
> 
> I have an interesting problem with Nagios event handlers, and I hope
> that someone here will find the problem interesting or be willing to
> help me.

<....>

> However, I'm having difficulty in making the script respond
> appropriately to Nagios events. A typical sequence of Nagios events,
> when I manually reboot one of the servers, goes like this:
> 
> * HOST DOWN
> * HOST UP
> * SERVICE CRITICAL (the host is "up", but the web server isn't running
> yet)
> * SERVICE OK (web server up and running)
> 
> At the moment, the script removes the host from the pool if either the
> host is DOWN, or the service is not OK. However, in the above 
> sequence,
> there is a "false OK" period after the host is reported UP, and before
> the service is reported CRITICAL. During this time, the host is in the
> pool when it shouldn't be.

You could disable host checks and base your event handler logic on service
results only (hard criticals and hard oks). I've done similar to avoid
confusion from badly timed check results triggering multiple event handler
instances etc.

-- 
Dan


-------------------------------------------------------
This SF.net email is sponsored by Microsoft Mobile & Embedded DevCon 2005
Attend MEDC 2005 May 9-12 in Vegas. Learn more about the latest Windows
Embedded(r) & Windows Mobile(tm) platforms, applications & content.  Register
by 3/29 & save $300 http://ads.osdn.com/?ad_id=6883&alloc_id=15149&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