Howto force a notification (before the schedul ed renotify time) for a down host/critical service ?

[Ton Voon]

On 12 Jul 2006, at 18:56, Tedman Eng wrote:

>> For instance, assume a service has a timeperiod of 05:00 to
>> 23:00 and
>> contacts have timeperiods of 24 hours. If the service fails at 3am,
>> Nagios will schedule the next check at 05:00. If it still fails at
>> 05:00, contacts will be notified.
>>
>
> That makes sense, that's how it's designed.  If ANY timeperiod  
> filter fails
> (service or contact timeperiod), the notification is not sent.  When a
> service renotifies, it will check the filters again during that  
> attempt.
> And again during the next re-notify attempt, and so on.

My understanding from the docs is that passing a service timeperiod  
acts differently than passing a contact timeperiod. Once a service  
timeperiod passes, the clock starts ticking for the next notification  
interval. So the two scenarios are not equivalent.


>> However, the converse is not true (and is arguably the more likely
>> scenario). Assume the service is 24 hours, but the contacts have a
>> timeperiod of 05:00 to 23:00. If the service fails at 3am, the
>> service is considered to be notified, but the filter for sending
>> notifications to contacts will fail. Contacts will not get
>> notification unless there is a notification retry.
>
> Same as above.  The 3am notification failed a timeperiod filter, so  
> the next
> renotification will test the filter again, and again, and so forth  
> until one
> of the re-notification attempts passes all timeperiod filters.

But this is the situation Stanley is asking for: how to get  
notifications of errors when a contact's timeperiod becomes available.

Let's say this: if the failure happened at 3am, the contact is not  
within timeperiod and *no* notification interval is set. The  
notification will never happen. I don't think this is right. I would  
expect, possibly naively, that I would get all the notifications, but  
only during the times I want.

Maybe you just should always set a notification interval. But it  
can't be too frequent because it would be annoying, but then that  
creates a longer lag time...

I did start by saying I didn't have any answers :)

Ton

http://www.altinity.com
T: +44 (0)870 787 9243
F: +44 (0)845 280 1725
Skype: tonvoon


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20060712/c51dc72b/attachment.html>
-------------- next part --------------

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
-------------- next part --------------
_______________________________________________
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