Page 2 of 2
Re: Nagios SNMP Trap alerting
Posted: Tue May 27, 2014 2:53 pm
by eloyd
http://nagios.sourceforge.net/docs/3_0/objectdefinitions.html#service
Look under "Directive Descriptions" for "max_check_attempts" and set this value to something higher than 1. You may need to combine this setting with "retry_interval" to get your hour long interval between successive failures before it alerts.
Re: Nagios SNMP Trap alerting
Posted: Wed May 28, 2014 11:33 am
by sreinhardt
I have specified escalation rule to notify me for the first time when the eth4 interface goes down 2 times in 1 hour. The test I did was to bring down eth4 and bring it up again. As per my escalation rules, I should not see active and passive check indicating the interface eth4 down and up. Yet, I still see in UI that the active check and passive check alert indicating that the interface was down and up.
Actually you have it configured to use the default service settings for the first notification. I don't see anything listing where that might go, my guess is that it's configured in a template we are not seeing. Then on the second service notification you are seeing your escalation go into effect. If you do not wish to see the first notification, you should create an escalation that sends to an invalid or local system address.