Passive service notification after X minutes

[Mohr James]

Hi All!

We have an application that sends SNMP traps to a trap server. Which
then uses send_nsca to send status changes. The application may notice a
problem and send a trap, thus changing the status of the Nagios service,
but the problem is self-correcting and the application may be Ok within
just a few seconds. However, the Nagios service has become critical and
thus send a notification. Not a happy thing at 2AM when you are sound
asleep.

Looking through the service definition I do not see anything that
applies. If it were an active service, I could use max_check_attempts.
However, in this cases, we only get the traps on every status change, so
if the service is down, the trap is set and thus the notification is
sent. Within the trap receiver, there is no way to wait a specific
period of time before sending the messages, only wait for X traps in Y
minutes.

I am at a loss as to how to get Nagios to wait for a specific length of
time before starting the notification other than creating some major
kludge like tweaking the notification mechanism somehow. Any help is
appreaciated.

Regards,

Jim Mohr

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
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