Re: [Nagios-devel] Flap detection based on time period instead of
Posted: Tue Oct 09, 2007 6:01 pm
------=_Part_8413_18011679.1191981704605
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
your example to me, looks like a special case that falls outside the box (I
hope someone else would clarify if I am wrong.)
If the service is being checked frequently via passive checks, why are the
Passive checks OK not being reported to nagios, (hypothetical question,
since there could be many reasons on why they are not reported)
It would make sence that this is the source of the Flapping not properly
refecting that service, and thus, flap detections should probobly be
disabled for that service.
tony (author of Nc_net)
On 10/9/07, Larry Low wrote:
>
> When setting up services that heavily rely on passive checks (only active
> monitor every 60 minutes or 12 hours, etc) it would be nice to base flap
> detection on state changes over a time period instead of the count of
> checks.
>
> Example:
>
> Interface status actively checked every 4 hours.
> 0:00 - Active Check OK
> 1:20 - Passive check causes CRTIICAL state.
> 1:25 - Passive check causes OK state.
> 4:00 - Active Check OK
> 8:00 - Active Check OK
> 9:29 - Passive check causes CRITICAL state.
> 10:00 - Passive check casues OK state.
>
> State change in this case is 5/7 (57%).
> If based on a time period of minutes you get 5/600 (.008%).
>
> Just an idea to allow for passive monitoring to be better handled with
> flap
> detection.
>
> ----
> Larry Low
> 4150 N Drinkwater Blvd., 5th Floor
> Scottsdale, AZ 85251
> E-mail: [email protected]'
>
> Telesphere Networks, Inc
>
>
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Nagios-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/lis ... gios-devel
>
------=_Part_8413_18011679.1191981704605
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
your example to me, looks like a special case that falls outside the box (I hope someone else would clarify if I am wrong.)
If the service is being checked frequently via passive checks, why are the Passive checks OK not being reported to nagios, (hypothetical question, since there could be many reasons on why they are not reported)
It would make sence that this is the source of the Flapping not properly refecting that service, and thus, flap detections should probobly be disabled for that service.
tony (author of Nc_net)
On 10/9/07, Larry Low <[email protected]> wrote:
When setting up services that heavily rely on passive checks (only activemonitor every 60 minutes or 12 hours, etc) it would be nice to base flap
detection on state changes over a time period instead of the count ofchecks.Example:Interface status actively checked every 4 hours.0:00 - Active Check OK1:20 - Passive check causes CRTIICAL state.
1:25 - Passive check causes OK state.4:00 - Active Check OK8:00 - Active Check OK9:29 - Passive check causes CRITICAL state.10:00 - Passive check casues OK state.State change in this case is 5/7 (57%).
If based on a time period of minutes you get 5/600 (.008%).Just an idea to allow for passive monitoring to be better handled with flapdetection.----Larry Low4150 N Drinkwater Blvd., 5th Floor
Scottsdale, AZ&nbs
...[email truncated]...
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
your example to me, looks like a special case that falls outside the box (I
hope someone else would clarify if I am wrong.)
If the service is being checked frequently via passive checks, why are the
Passive checks OK not being reported to nagios, (hypothetical question,
since there could be many reasons on why they are not reported)
It would make sence that this is the source of the Flapping not properly
refecting that service, and thus, flap detections should probobly be
disabled for that service.
tony (author of Nc_net)
On 10/9/07, Larry Low wrote:
>
> When setting up services that heavily rely on passive checks (only active
> monitor every 60 minutes or 12 hours, etc) it would be nice to base flap
> detection on state changes over a time period instead of the count of
> checks.
>
> Example:
>
> Interface status actively checked every 4 hours.
> 0:00 - Active Check OK
> 1:20 - Passive check causes CRTIICAL state.
> 1:25 - Passive check causes OK state.
> 4:00 - Active Check OK
> 8:00 - Active Check OK
> 9:29 - Passive check causes CRITICAL state.
> 10:00 - Passive check casues OK state.
>
> State change in this case is 5/7 (57%).
> If based on a time period of minutes you get 5/600 (.008%).
>
> Just an idea to allow for passive monitoring to be better handled with
> flap
> detection.
>
> ----
> Larry Low
> 4150 N Drinkwater Blvd., 5th Floor
> Scottsdale, AZ 85251
> E-mail: [email protected]'
>
> Telesphere Networks, Inc
>
>
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Nagios-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/lis ... gios-devel
>
------=_Part_8413_18011679.1191981704605
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
your example to me, looks like a special case that falls outside the box (I hope someone else would clarify if I am wrong.)
If the service is being checked frequently via passive checks, why are the Passive checks OK not being reported to nagios, (hypothetical question, since there could be many reasons on why they are not reported)
It would make sence that this is the source of the Flapping not properly refecting that service, and thus, flap detections should probobly be disabled for that service.
tony (author of Nc_net)
On 10/9/07, Larry Low <[email protected]> wrote:
When setting up services that heavily rely on passive checks (only activemonitor every 60 minutes or 12 hours, etc) it would be nice to base flap
detection on state changes over a time period instead of the count ofchecks.Example:Interface status actively checked every 4 hours.0:00 - Active Check OK1:20 - Passive check causes CRTIICAL state.
1:25 - Passive check causes OK state.4:00 - Active Check OK8:00 - Active Check OK9:29 - Passive check causes CRITICAL state.10:00 - Passive check casues OK state.State change in this case is 5/7 (57%).
If based on a time period of minutes you get 5/600 (.008%).Just an idea to allow for passive monitoring to be better handled with flapdetection.----Larry Low4150 N Drinkwater Blvd., 5th Floor
Scottsdale, AZ&nbs
...[email truncated]...
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]