Distributed Nagios and scheduling service chec k from the central server

[Tedman Eng]

> -----Original Message-----
> From: Marc Powell [mailto:marc at ena.com]
> Sent: Thursday, July 14, 2005 3:14 PM
> To: nagios-users at lists.sourceforge.net
> Subject: RE: [Nagios-users] Distributed Nagios and scheduling service
> check from the central server
> 
> 
> > -----Original Message-----
> > From: nagios-users-admin at lists.sourceforge.net [mailto:nagios-users-
> > Sent: Thursday, July 14, 2005 3:40 PM
> > To: nagios-users at lists.sourceforge.net
> > Subject: RE: [Nagios-users] Distributed Nagios and 
> > scheduling service check from the central server
> > ...
> > ...
> 
> 
> Active_checks_enabled 1
> Passive_checks_enabled 1
> check_period none
> check_freshness 1
> freshness_threshold 300 ; bad if 5 minutes old
> check_command some_valid_check_command
> 

Here is an important distinction: There are 2 ways to functionally "disable"
active checks for a distributed nagios environment.

Actve_checks_enabled 0
  -or-
check_period none


I prefer the "check_period=none", as this means that the active checks are
still enabled, but never get scheduled.  Downside is they sit in your queue
taking up space (unfortunately, at the top of the queue too).

In some instances, the central server will never be able to perform the
active check, so  completely disabling the active check for those services
would be the way to go, and they won't go into the queue.


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
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