How to have a service only alert on the 2nd or 3rd 'unavailable' alert?

[Babineau, Mike]

Yes, and I believe Nagios is configured in that way by default.  See
"max_check_attemps" here:
http://nagios.sourceforge.net/docs/2_0/xodtemplate.html#service

-----Original Message-----
From: nagios-users-bounces at lists.sourceforge.net
[mailto:nagios-users-bounces at lists.sourceforge.net] On Behalf Of Patrick
- South Valley Internet
Sent: Tuesday, May 08, 2007 11:11 AM
To: nagios-users at lists.sourceforge.net
Subject: [Nagios-users] How to have a service only alert on the 2nd or
3rd 'unavailable' alert?

Hi all,

We have a service we are monitoring that there is something screwy at 
their location.  It will go down, then 2 seconds later go back up.  We 
want Nagios to only page us if it goes down for a longer period of time,

let's say the 2nd or 3rd time Nagios sees that it is not pingable.

Is this possible?

------------------------------------------------------------------------
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
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 DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
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