Disable checking but keep in OK state

[Hari Sekhon]

Mark Clarkson wrote:
>> On Tue, 13 May 2008 08:11:35 -0500, Jim.Melin at co.hennepin.mn.us wrote:
>> Yes. Select the service check in question (provided that you have the
>> ability to submit commands and the like enabled), and you'll see teh
>> service
>> state information  screen. Over on the right, under Service Commnds,
>> select "Disable active checks of this service" and then "submit passive
>> check
>> results for this service" and make up your own check output and
>> performance data.
>>
>> That will leave it green and happy until your turn active checking back
>> on.
>>
>> -J
>>
>>     
>
> This works great! Thanks for such a quick response.
>
> Cheers
> Mark.
>   
If these services are dynamic, then how do you know which server to 
connect to, do you have them DNS aliased or something, or perhaps you 
just try all of the servers until you find one running and use that?

Some possibilities:

1. If using DNS then put the dns alias as the hostname in the check so 
the check will always point to the right machine by following dns.
2. If you just try any of the servers, you could write a wrapper script 
to run the check against through all of them in sequence and to exit on 
the first working one, or return critical if none of them work.

Just a stab in the dark given the limited info. Disabling service checks 
manually doesn't sound like a good idea if these services really are 
dynamic... you'd have to do this manually a lot?

-h

-- 
Hari Sekhon


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft 
Defy all challenges. Microsoft(R) Visual Studio 2008. 
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
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