passive checks for non-24x7 hosts going stale outside check_period

[Mark Wagner]

I have a distributed set-up where the web interface server never
does any checks. Freshness checking is enabled on the web interface
server with a check command that will alert that the service/host
is stale.

Everything works fine except for those hosts that are not monitored
24x7.

For example, services/hosts that are monitored 9am-5pm will be reported as
stale every morning at 9am. The service/host goes stale on the active
monitoring servers too, a service/host check will be forced, and the
result will be sent to the web interface server at which point the web
interface server is happy again.

I would think that Nagios would not include time outside of
the check_period when calculating how fresh a service/host is
but that appears not to be the case. (Please correct me if I
am wrong.)

Does anybody have any tips on how to handle this situation?

I'm using Nagios v2.9.

-- 
Mark Wagner <markwag at u.washington.edu>
System Administrator, UW Medicine IT Services

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
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