In version 1.x flap-detection supresses all notifications, even recovery notifications. :(
This behavior may have changed/improved in version 2.x, though I can't say for certain. > -----Original Message----- > From: Andrea Gabellini [mailto:[EMAIL PROTECTED] > Sent: Friday, January 27, 2006 5:01 AM > To: nagios-users > Subject: [Nagios-users] Service flapping/recovery > > > Hi, > > I noticed a strange behavior of a service. Nagios send > regularly the notification on critical state. > After that the service start flapping and then recover from > flapping and critical state. But Nagios > doesn't send the recovery notifiocation. The > notification_options for this service is setup as 'c,r'. > > This is a bug or a feature? > > Attached a recent alarm history. > > > > January 27, 2006 10:00 > Service stopped flapping[27-01-2006 10:16:38] SERVICE > FLAPPING ALERT: rt_backend;CPU_CISCO;STOPPED; > Service appears to have stopped flapping (3.8% change < 5.0% > threshold) > > January 27, 2006 09:00 > Service Ok[27-01-2006 09:38:29] SERVICE ALERT: > rt_backend;CPU_CISCO;OK;HARD;3;CPU Load: 47% (1 min) - OK > Service Warning[27-01-2006 09:36:29] SERVICE ALERT: > rt_backend;CPU_CISCO;WARNING;HARD;3;CPU Load: > 63% (1 min) > 50 - WARNING > Service started flapping[27-01-2006 09:34:30] SERVICE > FLAPPING ALERT: rt_backend;CPU_CISCO;STARTED; > Service appears to have started flapping (22.6% change >= > 20.0% threshold) > Service Critical[27-01-2006 09:34:29] SERVICE ALERT: > rt_backend;CPU_CISCO;CRITICAL;HARD;3;CPU Load: > 80% (1 min) > 75 - CRITICAL > Service Warning[27-01-2006 09:32:29] SERVICE ALERT: > rt_backend;CPU_CISCO;WARNING;HARD;3;CPU Load: > 68% (1 min) > 50 - WARNING > Service Critical[27-01-2006 09:26:29] SERVICE ALERT: > rt_backend;CPU_CISCO;CRITICAL;HARD;3;CPU Load: > 80% (1 min) > 75 - CRITICAL > Service Warning[27-01-2006 09:08:29] SERVICE ALERT: > rt_backend;CPU_CISCO;WARNING;HARD;3;CPU Load: > 61% (1 min) > 50 - WARNING > Service Warning[27-01-2006 09:07:29] SERVICE ALERT: > rt_backend;CPU_CISCO;WARNING;SOFT;2;CPU Load: > 54% (1 min) > 50 - WARNING > Service Warning[27-01-2006 09:06:29] SERVICE ALERT: > rt_backend;CPU_CISCO;WARNING;SOFT;1;CPU Load: > 56% (1 min) > 50 - WARNING > Service Ok[27-01-2006 09:02:29] SERVICE ALERT: > rt_backend;CPU_CISCO;OK;SOFT;2;CPU Load: 42% (1 min) - OK > Service Warning[27-01-2006 09:01:29] SERVICE ALERT: > rt_backend;CPU_CISCO;WARNING;SOFT;1;CPU Load: > 53% (1 min) > 50 - WARNING > -- > > --------------------------------------- > Psssst! Hey you! Look out! Behind you! > --------------------------------------- > Ing. Andrea Gabellini > Email: [EMAIL PROTECTED] > Tel: 0549 886111 (Italy) > Tel. +378 0549 886111 (International) > > Telecom Italia San Marino S.p.A. > Strada degli Angariari, 3 > 47891 Rovereta > Repubblic of San Marino > > http://www.omniway.sm http://www.telecomitalia.sm > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep > through log files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. > DOWNLOAD SPLUNK! > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&; dat=121642 _______________________________________________ Nagios-users mailing list [email protected] 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: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ Nagios-users mailing list [email protected] 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
