Checking freshness Time period

[Florian.Kirchmeir at infineon.com]

Hi all!

I'd rather tie the freshness-checking to the check_period than the
notification_period.
I may have a restricted notification period (e.g., only notify during
office hours), but still require freshness checking for the service
24x7, or some other time period.

Regarding the retry interval: Hm, might be a nice feature, yes. I can
think of a scenario where this would be really necessary, though. Can
you come up with a good example?

Regards,
Florian

-----Original Message-----
From: Sumit Malhotra [mailto:smalhotra at dataarmor.net] 
Sent: Freitag, 25. Juni 2004 06:32
To: Kirchmeir Florian (IFAT IT OS)
Cc: Nagios List
Subject: Re: [Nagios-users] Checking freshness Time period


Hi All!!

I found the problem . Its more of Architecture issue in nagios

 The Passive check and active check when used separately works great !

But problem comes when the both need  to be used simultaneously. Like in
condition where the active checks needs to be forced  when  the results
from the passive checks are not received ..

The following requirements may be added to the coming version ( May be
in 2.0 its there  ... I haven't checked it ):

1. The number of Retry checks by  passive check and Active Check  ( the
number of soft state the service should be):  They should be separate,
if used in conjunction.  As I would like the number of active checks to
be retried once. if the passive checks are not being received.

2. Notification period: The freshness check should be checked only in
notification period stated in the definition.( or a separate parameter
can be added)

What do you think  florian ???

Regards,
Sumit
----- Original Message -----
From: <Florian.Kirchmeir at infineon.com>
To: <smalhotra at dataarmor.net>
Cc: <nagios-users at lists.sourceforge.net>
Sent: Wednesday, June 23, 2004 7:33 PM
Subject: RE: [Nagios-users] Checking freshness Time period


Uhm, maybe I didn't make myself clear:
Of course freshnes-checking should be done during the times defined as
check_period. Outside those hours, when no service-check results are
expected, freshness checking should be suspended.

The way I understand your original post, that's what you would expect
Nagios to do, right?

Regards,
Florian

-----Original Message-----
From: Sumit Malhotra [mailto:smalhotra at dataarmor.net]
Sent: Mittwoch, 23. Juni 2004 15:40
To: Kirchmeir Florian (IFAT IT OS)
Cc: Nagios List
Subject: Re: [Nagios-users] Checking freshness Time period


Hi Florian,

The need for Freshness check is there in every case of NSCA.As  you will
not get any alert  if you didn't get the passive check  fo a service at
all.( no Alert no action)

Freshness check  helps you in those cases .( Which has no relation with
Notification period --- i am assuming)

Regards,
Sumit

----- Original Message -----
From: <Florian.Kirchmeir at infineon.com>
To: <nagios-users at lists.sourceforge.net>
Cc: <smalhotra at dataarmor.net>; <nagios-devel at lists.sourceforge.net>
Sent: Wednesday, June 23, 2004 4:33 PM
Subject: Re: [Nagios-users] Checking freshness Time period


Hi all!

Crossposting to nagios-devel, since this is rather a feature request.
Sumit, as far as I understand, there is currently no (simple) way to
make this work.

Currently, you make a service "passive" by setting the check_period to
"none". To me, this is rather a hack; it adds a side-affect to a
configuration option that isn't obvious, and actually reduces
functionallity. I'd prefer being able to set the check_period for
passive services just like for active ones, and make it passive by
explicitly setting "passive_checks_enabled=1" and
"active_checks_enabled=0". Service-check results received outside the
check_period (or rather: having a timestamp outside it; regardless of
when it's received) should be discarded, and no freshness-checking
should be performed.

Please correct me if I'm wrong, and things do already work that way! It
wasn't when I last checked...

Regards,
Florian Kirchmeir


----- Original Message -----=
From: "Sumit Malhotra" <smalhotra at dataarmor.net>
To: "Nagios List" <nagios-users at lists.sourceforge.net>
Subject: Re: [Nagios-users] Checking freshness Time period
Date: Mon, 14 Jun 2004 20:31:08 +0530

This is a multi-part message in MIME format.

------=_NextPart_000_013F_01C4524E.860333A0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Can anybody help on this ????

-Sumit

  ----- Original Message -----=20
  From: Sumit Malhotra=20
  To: Nagios List=20
  Sent: Friday, June 11, 2004 3:20 PM
  Subject: [Nagios-users] Checking freshness Time period


  Hi ,

   I am using nagios 1.2 and nsca in combination . Both works great =
together.

  I have configured for freshness check evrey 15 minutes( As shown =
below) . In case it fails an alert is genrated via command noreport. It
= works fine for 24*7 monitoring of services

  Problem comes when i want some service to be checked for 16*5 . I get
= alerts even when i have configured the service are configured for =
16*5(check period) ( Although i am able to suppress teh alerts using =
notification period i.e. by setting it to 16*5) but still there is a red
= alert in the web interface .I would have loved to get a wall of
"GREEN".











-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Nagios-users mailing list
Nagios-users at 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