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

Roderick A. Anderson raanders at cyber-office.net
Wed Jun 16 16:54:49 CEST 2010


Roderick A. Anderson wrote:
> 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.

My thanks to all for your suggestions and ideas.

I now have it working correctly without even having to run a test. ;-)

Had a hardware failure yesterday that triggered the Service.  :-(  It 
kept sending notifications every five minutes until the problem was solved.


\\||/
Rod
-- 
> 
> 
> 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





More information about the Users mailing list