Need guidance on specific approach

[Kevin Keane]

Good point about the freshness. I didn't explain how I am doing that. 
First of all, I am assuming that your scripts all run at regular 
intervals? If you have a script that, say, runs only Wednesdays and 
Thursdays but not the other days, getting it right will be tricky.

In my case, the script runs daily. I want to be notified if it hasn't 
been running for three days in a row - a bit more relaxed requirement 
than yours. So I simply set the freshness interval to 72 hours.

If you have a script that runs, say, once a week at midnight, and want 
to be alerted the next day at 6 AM that it didn't run, it will be 
trickier to get the freshness interval just right. In that case, you 
probably should be using 172 hours. One week is 168 hours - but you need 
to allow some additional time for the script to run.

I don't know how that fits with the time periods, though. I'm only using 
the 24x7 time period so far.

Joseph L. Casale wrote:
>> The idea is to create a passive check for each of your scripts. When the
>> script completes successfully, use send_nsca to send the result to the
>> Nagios server. Optionally, I am also sending a check result when the
>> script starts, and if it completes with an error.
>>     
>
> Actually this would be accomplish all that I need!
>
>   
>> The part I can't help you with is how to actually do a send_nsca from
>> Windows. I think send_nsca exists for Windows as well, but if not, you
>> might have to cobble something together using NSClient++.
>>     
>
> I found a native win32 nsca client at www.monitoringexchange.org as well.
>
>   
>> If I understand you right, you also have the problem that you have too
>> many scripts and don't want to modify each one for monitoring? If that's
>> the case, simply write a wrapper script that calls the actual script
>> based on a command-line argument. Then change all your scheduler entries
>> to call that wrapper instead of the actual script. That wrapper script
>> could accept additional arguments so you can also specify the text in
>> the check result to be used.
>>     
>
> I don't mind modifying the scripts, I just meant I had to many so as to monitor
> all of them and Nagios was a pain when I might see it all in Nagios. I assume as
> not all of my scripts run every day, I can use Time Periods to restrict the checking
> but how does that work with the check_dummy and freshness_threshold? My scripts
> are much shorter and I need to know the day after if they didn't run so the
> freshness_threshold will be much lower than the weekend span? How do I stop an
> erroneous critical event every weekend for example?
>
> Thanks for the ideas!
> jlc
>   

-- 
Kevin Keane
Owner
The NetTech
Find the Uncommon: Expert Solutions for a Network You Never Have to Think About

Office: 866-642-7116
http://www.4nettech.com

This e-mail and attachments, if any, may contain confidential and/or proprietary information. Please be advised that the unauthorized use or disclosure of the information is strictly prohibited. The information herein is intended only for use by the intended recipient(s) named above. If you have received this transmission in error, please notify the sender immediately and permanently delete the e-mail and any copies, printouts or attachments thereof.


------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time, 
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize  
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
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