[Q] Service config, go critical:HARD; Alert every 5 minutes until non-critical

[Giorgio Zarrelli]

Hi,

have a look at my little 2 cents on escalations, it will show you how  
the checks timings and notification work.


http://www.zarrelli.org/blog/2010/04/26/nagios-notification-escalations-made-easy/

Ciao,

Giorgio

Il giorno 14/giu/2010, alle ore 17.03, "Roderick A. Anderson" <raanders at cyber-office.net 
 > ha scritto:

> My Nagios foo must leave a lot to be desired.  8-(
>
> I have not been able to figure out the correct combination of service
> definition settings to get a check to go CRITICAL:HARD on the first  
> try
> (no SOFT alerts), and keep sending alerts (every five minutes) until  
> the
> check/alert clears.
>
> Either the complete answer or a clue-stick whack (the settings I  
> should
> be looking at) would be greatly appreciated.
>
>
> TIA,
> Rod
> -- 
>
>
> --- 
> --- 
> --- 
> ---------------------------------------------------------------------
> ThinkGeek and WIRED's GeekDad team up for the Ultimate
> GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
> lucky parental unit.  See the prize list and enter to win:
> http://p.sf.net/sfu/thinkgeek-promo
> _______________________________________________
> 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

------------------------------------------------------------------------------
ThinkGeek and WIRED's GeekDad team up for the Ultimate 
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the 
lucky parental unit.  See the prize list and enter to win: 
http://p.sf.net/sfu/thinkgeek-promo
_______________________________________________
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