Is there a way to prevent a host check in agive time period?

[Greg Vickers]

Riiight I see ... <scratches head> I'm sorry I can't add anything else 
useful except reiterate what has been stated before - if service checks 
aren't scheduled to run during that timeperiod then there shouldn't be 
any hostcheck performed and host notifications should not be sent our or 
queued!!

So are you using that timeperiod for your notification_period for that 
host? According to this: 
http://your_server/nagios/docs/xodtemplate.html#host, 
"notification_period: 	This directive is used to specify the short name 
of the time period during which notifications of events for this host 
can be sent out to contacts. If a host goes down, becomes unreachable, 
or recoveries during a time which is not covered by the time period, no 
notifications will be sent out." Does this not meet your requirement? It 
seems that notifications should not be queued during this timeperiod if 
a host check is somehow scheduled to run during this time.

I would also suggest checking the value of your check_period for the 
services on that host are correct to exclude this time?

HTH,
Greg

Erik Spigle wrote:
> That doesn't work as expected per my original message on 02/25/05.  You can specify a new time period that indicates the "dead time" and then set that as the time period for the service check / notification and host notification, but host checks still happen as you cannot specify a "check_period" -- only notifcation period for the host.  When the host check fires off and fails, it queues up a notification then fires it off after the dead time is over.  
> 
> Here is a scenario to give example.  We set a new time period that is 00:00-03:00,04:00-24:00.  We use this time period on a specific server that we want absolutely no checks or notifications for the host or services between the hours of 03:00am and 04:00am every day.  It succeeds in not doing any service checks or notifications during this time period.  For the host portion, it manages not to notify *between 03:00am and 04:00am*.  It still must perform some type of check, though, as it fires off a notification if it saw anything happen during this hour as soon as 04:00am rolls around.
> 
> Someone previously mentioned it could have something to do with freshness checking, but didn't go any further with details on what I might want to look into.  Do I want to completely turn freshness checking off?  Exactly what do I need to do to make the host check not happen during this hour so it doesn't queue up a notfication after this hour passes?
> 
> Thanks.
> 
> -----Original Message-----
> From: nagios-users-admin at lists.sourceforge.net
> [mailto:nagios-users-admin at lists.sourceforge.net]On Behalf Of Greg
> Vickers
> Sent: Monday, February 28, 2005 5:33 PM
> Cc: Nagios-users at lists.sourceforge.net
> Subject: Re: [Nagios-users] Is there a way to prevent a host check in
> agive time period?
> 
> 
> There sure is a way - change the timeperiod defined for that host check 
> / notification so the timeperiod excludes that time frame. Then Nagios 
> will not perform a check or send notifications during that time.
> 
> HTH,
> Greg
> 
> Erik Spigle wrote:
> 
>>Is there a way, then, to prevent a host check / notification from ever happening during a specific timeframe?  It doesn't really mean much if you can prevent a host notification from happening during a specific timeframe only for it to fire off immediately when that timeframe is up because it checked the host anyway and queued up a notification.
>>
>>-----Original Message-----
>>From: jeff vier [mailto:boinger at tradingtechnologies.com]
>>Sent: Friday, February 25, 2005 11:08 AM
>>To: Erik Spigle
>>Cc: nagios-users
>>Subject: Re: [Nagios-users] Is there a way to prevent a host check in
>>agive time period?
>>
>>
>>On Fri, 2005-02-25 at 10:29 -0600, Erik Spigle wrote:
>>
>>
>>>Why is there a "check_period" directive for service definitions, but not for host definitions?
>>
>><chop>
>>
>>because host checks only "go off" if that host has a service alert.
>>
>>
>>
>>>it still did a host check during this period
>>
>>
>>Why you got a host check fired off is likely an issue of freshness
>>checking overriding your timeperiod (or, perhaps something else...hard
>>to say offhand).
>>
>>
>>
>>-------------------------------------------------------
>>SF email is sponsored by - The IT Product Guide
>>Read honest & candid reviews on hundreds of IT Products from real users.
>>Discover which products truly live up to the hype. Start reading now.
>>http://ads.osdn.com/?ad_ide95&alloc_id396&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
>>
> 
> 

-- 
Greg Vickers
Computer Systems Officer
Teaching and Learning Support Services
Information Technology Services
Queensland University of Technology

email: g.vickers at qut.edu.au
phone: (07) 3864 8276
mobile: 0416 001 674, SD #6 6147

CIROS code: 00213J


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&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