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

Ton Voon ton.voon at altinity.com
Wed Jul 12 10:53:49 CEST 2006


Hi Stanley,


On 12 Jul 2006, at 00:40, <Stanley.Hopcroft at Dest.gov.au>  
<Stanley.Hopcroft at Dest.gov.au> wrote:

> I would like to do this to send out notifications after a period of
> no-notifications ends (we
> have the view that people do not react well to even major crises  
> between
> about midnight and 4-5 am so
> we don't send notifications during that period. However it would be  
> nice
> to send out all the
> notifications for outages that occurred in the no-notification  
> period at
> 5 am).

Sorry, no solutions, just more questions :)

We had it reported to us, but we haven't investigated further, that  
notifications do not get resent for a contact who has a timeperiod  
outside the original failure.

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.

Here's the section that says so in the docs: http:// 
nagios.sourceforge.net/docs/2_0/notifications.html:

[quote]

Note: If the [host or service] time period filter is not passed,  
Nagios will reschedule the next notification for the host or service  
(if its in a non-OK state) for the next valid time present in the  
time period. This helps ensure that contacts are notified of problems  
as soon as possible when the next valid time in time period arrives.

[end quote]

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.

We haven't investigated further, but, if the design documented at  
http://nagios.sourceforge.net/docs/2_0/notifications.html is  
accurate, that would be the case.

I'm not sure what the long-term fix is. Maybe notification_number per  
contact? Perhaps scheduling of notifications? This is probably one  
for Ethan.

Ton


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




-------------------------------------------------------------------------
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
_______________________________________________
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





More information about the Users mailing list