[Nagios-devel] Feature request

Christoph Maser cmr at financial.com
Fri Jan 12 15:51:18 UTC 2007


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Mayby you should stick to the docs instead of ignoring them. Using
passive, volatile checks which run regularly and have freshness checking
enabled is the right solution for something like cron-jobs,
smart-monitoring etc. Also this belongs on nagios-users and not to
nagios-devel!

Chris

Thomas Guyot-Sionnest wrote:
>> -----Original Message-----
>> From: nagios-devel-bounces at lists.sourceforge.net 
>> [mailto:nagios-devel-bounces at lists.sourceforge.net] On Behalf 
>> Of Nicolas COLIN
>> Sent: January 12, 2007 3:54
>> To: nagios-devel at lists.sourceforge.net
>> Subject: Re: [Nagios-devel] Feature request
>>
>> Christoph Maser <cmr <at> financial.com> writes:
>>> Hi,
>>>
>>> this is not a good idea. You will never know if your 
>> services are just
>>> stale. Make your checks report periodically (e.g. once a 
>> day) report an
>>> OK status themselves and add freshness checking. Otherwise 
>> you will not
>>> know if the service actually works.
>>>
>>> Chris
>>>
>> You can easily set the status by sending a file containing 
>> the following lines
>> to the FIFO.
>>
>> [1165913959] PROCESS_SERVICE_CHECK_RESULT;Server;Service;0;
>>
>> I prepared a file containing this for all the servers and all 
>> the services I
>> configure as passive check and send it ( cat [file_name] >
>> /usr/local/nagios/var/rw/nagios.cmd ) whenever I want to set 
>> to OK ( In fact, I
>> just do it once at the installation ).
> 
> Are you guys talking about volatile services, like receiving traps?
> 
> Contrary to what suggests the doc I set them as Active with the following
> additionnal config:
> 
>   check_command          check_dummy!0!"Trap reset on $LONGDATETIME$"
>   check_period           none
>   max_check_attempts     1
>   is_volatile            1
>   flap_detection_enabled 0
>   notification_options   w,u,c
>   stalking_options       w,u,c
> 
> The active check never gets scheduled but to reset the trap all I have to do
> is schedule an active check.
> 
> Maybe Nagios could be modified to run an initial check on active volatile
> services with check_period set to "none". That would not impact passive
> checks and this could be a configurable option. However it doesn't solve the
> problem when for some reason you get many/all your traps triggered off and
> want to reset them all-.
> 
> I attached the script I use to reset all traps. If you have also many
> different checks it could be modified to loop over a list of services as
> well. If the service doesn't exists on some hosts it just gets ignored. The
> best would be a perl version that create a list of servers and their
> passive/volatile services out of the status file.
> 
> Thomas
> 
> 
> ------------------------------------------------------------------------
> 
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Nagios-devel mailing list
> Nagios-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nagios-devel
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
Comment: Using GnuPG with CentOS - http://enigmail.mozdev.org

iD8DBQFFp651sLjW0HYht7URAr+dAKC7JW2Pl7tj0HqJ975+lSRy30nX0QCglncd
3js1fTWWDz0sUszs+o0rbq4=
=daKg
-----END PGP SIGNATURE-----




More information about the Nagios-devel mailing list