Re: [Nagios-users] Clearing previous flapping states?

2011-07-01 Thread Tim Philips

Thanks very much!  

I thought and suspected as much but didn't know if I was missing something with 
regards to being able to clear flapping.


On 1/07/2011, at 1:39 AM, m...@catsnest.co.uk wrote:

 On Thu, Jun 30, 2011 at 12:19 PM, Jim Avery j...@jimavery.me.uk wrote:
 On 30 June 2011 11:42, Tim Philips t...@rndgroup.co.nz wrote:
 Hi All,
 
 Tell me, is it possible to pass a command to the Nagios command file to 
 clear (previous) flapping?  I'm picking no - based on my understanding of 
 the documentation but thought I would ask.
 
 The scenario is we have a number of check software updates that run and 
 as such we schedule these daily.  There is a scenario within the flapping 
 period where there are and aren't updates some of the future warning or 
 critical warnings get suppressed.
 
 The simple answer that springs to mind for me is to disable flapping for 
 things that are scheduled over x number of hours.  How are other people 
 dealing with such things?
 
 You're right - there is no command you can pass to Nagios to clear the
 previous flapping state.  You could try disabling flap detection and
 then enabling it again, but my guess is that Nagios will immediately
 re-assess the flapping state based on the last 21 checks as soon as
 you re-enable flap detection and you'll be back where you started.
 
 If your checks are only run daily, then I would say almost certainly
 flap detection is of no benefit to you and should be disabled for
 those services.  If Nagios is basing it's assessment of whether the
 service is flapping on the last 21 checks as described in the
 documentation (
 http://nagios.sourceforge.net/docs/nagioscore/3/en/flapping.html ),
 then since your checks are daily, it could be a couple of weeks
 sometimes before Nagios decides that flapping has stopped!
 
 IMHO, flap detection is only usually useful for those services which
 are checked quite frequently.
 
 
 Yup we do the same thing, eg have flap detection disabled in the
 service template for long interval checks.
 The only way I know to clear the flapping status, is to cheat and
 manually schedule the check a load of times (or submit passive checks
 ;)
 
 --
 Ritchie
 
 --
 All of the data generated in your IT infrastructure is seriously valuable.
 Why? It contains a definitive record of application performance, security
 threats, fraudulent activity, and more. Splunk takes this data and makes
 sense of it. IT sense. And common sense.
 http://p.sf.net/sfu/splunk-d2d-c2
 ___
 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
 
 
 --
 All of the data generated in your IT infrastructure is seriously valuable.
 Why? It contains a definitive record of application performance, security 
 threats, fraudulent activity, and more. Splunk takes this data and makes 
 sense of it. IT sense. And common sense.
 http://p.sf.net/sfu/splunk-d2d-c2
 ___
 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

--
Thanks,

Tim Philips (RHCE)
RND GROUP LIMITED


--
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security 
threats, fraudulent activity, and more. Splunk takes this data and makes 
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
___
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


[Nagios-users] Clearing previous flapping states?

2011-06-30 Thread Tim Philips
Hi All,

Tell me, is it possible to pass a command to the Nagios command file to clear 
(previous) flapping?  I'm picking no - based on my understanding of the 
documentation but thought I would ask.

The scenario is we have a number of check software updates that run and as 
such we schedule these daily.  There is a scenario within the flapping period 
where there are and aren't updates some of the future warning or critical 
warnings get suppressed.  

The simple answer that springs to mind for me is to disable flapping for things 
that are scheduled over x number of hours.  How are other people dealing with 
such things?


--
Thanks,

Tim Philips (RHCE)
RND GROUP LIMITED


--
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security 
threats, fraudulent activity, and more. Splunk takes this data and makes 
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
___
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] Clearing previous flapping states?

2011-06-30 Thread Jim Avery
On 30 June 2011 11:42, Tim Philips t...@rndgroup.co.nz wrote:
 Hi All,

 Tell me, is it possible to pass a command to the Nagios command file to clear 
 (previous) flapping?  I'm picking no - based on my understanding of the 
 documentation but thought I would ask.

 The scenario is we have a number of check software updates that run and as 
 such we schedule these daily.  There is a scenario within the flapping 
 period where there are and aren't updates some of the future warning or 
 critical warnings get suppressed.

 The simple answer that springs to mind for me is to disable flapping for 
 things that are scheduled over x number of hours.  How are other people 
 dealing with such things?

You're right - there is no command you can pass to Nagios to clear the
previous flapping state.  You could try disabling flap detection and
then enabling it again, but my guess is that Nagios will immediately
re-assess the flapping state based on the last 21 checks as soon as
you re-enable flap detection and you'll be back where you started.

If your checks are only run daily, then I would say almost certainly
flap detection is of no benefit to you and should be disabled for
those services.  If Nagios is basing it's assessment of whether the
service is flapping on the last 21 checks as described in the
documentation (
http://nagios.sourceforge.net/docs/nagioscore/3/en/flapping.html ),
then since your checks are daily, it could be a couple of weeks
sometimes before Nagios decides that flapping has stopped!

IMHO, flap detection is only usually useful for those services which
are checked quite frequently.

--
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security 
threats, fraudulent activity, and more. Splunk takes this data and makes 
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
___
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] Clearing previous flapping states?

2011-06-30 Thread mail
On Thu, Jun 30, 2011 at 12:19 PM, Jim Avery j...@jimavery.me.uk wrote:
 On 30 June 2011 11:42, Tim Philips t...@rndgroup.co.nz wrote:
 Hi All,

 Tell me, is it possible to pass a command to the Nagios command file to 
 clear (previous) flapping?  I'm picking no - based on my understanding of 
 the documentation but thought I would ask.

 The scenario is we have a number of check software updates that run and as 
 such we schedule these daily.  There is a scenario within the flapping 
 period where there are and aren't updates some of the future warning or 
 critical warnings get suppressed.

 The simple answer that springs to mind for me is to disable flapping for 
 things that are scheduled over x number of hours.  How are other people 
 dealing with such things?

 You're right - there is no command you can pass to Nagios to clear the
 previous flapping state.  You could try disabling flap detection and
 then enabling it again, but my guess is that Nagios will immediately
 re-assess the flapping state based on the last 21 checks as soon as
 you re-enable flap detection and you'll be back where you started.

 If your checks are only run daily, then I would say almost certainly
 flap detection is of no benefit to you and should be disabled for
 those services.  If Nagios is basing it's assessment of whether the
 service is flapping on the last 21 checks as described in the
 documentation (
 http://nagios.sourceforge.net/docs/nagioscore/3/en/flapping.html ),
 then since your checks are daily, it could be a couple of weeks
 sometimes before Nagios decides that flapping has stopped!

 IMHO, flap detection is only usually useful for those services which
 are checked quite frequently.


Yup we do the same thing, eg have flap detection disabled in the
service template for long interval checks.
The only way I know to clear the flapping status, is to cheat and
manually schedule the check a load of times (or submit passive checks
;)

--
Ritchie

 --
 All of the data generated in your IT infrastructure is seriously valuable.
 Why? It contains a definitive record of application performance, security
 threats, fraudulent activity, and more. Splunk takes this data and makes
 sense of it. IT sense. And common sense.
 http://p.sf.net/sfu/splunk-d2d-c2
 ___
 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


--
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security 
threats, fraudulent activity, and more. Splunk takes this data and makes 
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
___
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