[Nagios-users] Antwort: How to not send out first service notifications?
[EMAIL PROTECTED] schrieb am 19.10.2006 11:04:19: I am monitoring some hosts on the Internet for informational reasons. Since these hosts quite frequently have failed services, I'd like my Nagios to refrain from notifying me if a service is down at the first notification. Subsequent notifications, however, should be sent out. Is there a way to do this any easier than having no notifications set in the service definition and have a service escalation having the list of contacts that used to be in the service definition? If you always only want the 2nd notification, then your approach sounds wrong. You shouldn't suppress the first notification always, but instead maybe raise the number of consecutive failed checks until you throw a hard state, so you do not get too many false warnings. regards Sascha -- Sascha Runschke Netzwerk Management IT-Services ABIT AG Robert-Bosch-Str. 1 40668 Meerbusch Tel.:+49 (0) 2150.9153.226 Mobil:+49 (0) 173.5419665 mailto:[EMAIL PROTECTED] http://www.abit.net http://www.abit-epos.net - Sicherheitshinweis zur E-Mail Kommunikation / Security note regarding email communication: http://www.abit.net/sicherheitshinweis.html - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Nagios-users mailing list Nagios-users@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
Re: [Nagios-users] Antwort: How to not send out first service notifications?
On Thu, Oct 19, 2006 at 11:10:56AM +0200, [EMAIL PROTECTED] wrote: [EMAIL PROTECTED] schrieb am 19.10.2006 11:04:19: I am monitoring some hosts on the Internet for informational reasons. Since these hosts quite frequently have failed services, I'd like my Nagios to refrain from notifying me if a service is down at the first notification. Subsequent notifications, however, should be sent out. Is there a way to do this any easier than having no notifications set in the service definition and have a service escalation having the list of contacts that used to be in the service definition? If you always only want the 2nd notification, then your approach sounds wrong. You shouldn't suppress the first notification always, but instead maybe raise the number of consecutive failed checks until you throw a hard state, so you do not get too many false warnings. Actually, it is fine (and desired) for the service to show up in the web interface as DOWN, and that the history is correctly written. Greetings Marc -- - Marc Haber | I don't trust Computers. They | Mailadresse im Header Mannheim, Germany | lose things.Winona Ryder | Fon: *49 621 72739834 Nordisch by Nature | How to make an American Quilt | Fax: *49 621 72739835 - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Nagios-users mailing list Nagios-users@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
Re: [Nagios-users] Antwort: How to not send out first service notifications?
Marc Haber wrote: On Thu, Oct 19, 2006 at 11:10:56AM +0200, [EMAIL PROTECTED] wrote: [EMAIL PROTECTED] schrieb am 19.10.2006 11:04:19: I am monitoring some hosts on the Internet for informational reasons. Since these hosts quite frequently have failed services, I'd like my Nagios to refrain from notifying me if a service is down at the first notification. Subsequent notifications, however, should be sent out. Is there a way to do this any easier than having no notifications set in the service definition and have a service escalation having the list of contacts that used to be in the service definition? If you always only want the 2nd notification, then your approach sounds wrong. You shouldn't suppress the first notification always, but instead maybe raise the number of consecutive failed checks until you throw a hard state, so you do not get too many false warnings. Actually, it is fine (and desired) for the service to show up in the web interface as DOWN, and that the history is correctly written. They still will, as availability times are calculated from the first failed check, and the GUI shows things in the state they are at the moment of displaying it, regardless of it being a soft or hard state. Only notification behaviour is modified if you fiddle with the max_check_attempts and retry_check_interval variables. -- Andreas Ericsson [EMAIL PROTECTED] OP5 AB www.op5.se Tel: +46 8-230225 Fax: +46 8-230231 - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Nagios-users mailing list Nagios-users@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
