Service escalations not working as expected?
Andreas Ericsson
ae at op5.se
Mon Jan 10 13:01:17 CET 2005
Luca Corti wrote:
> Hello,
>
> I've got the following service escalation in place.
>
> define serviceescalation {
> host_name MYHOST
> service_description Disk Usage
> first_notification 1
> last_notification 2
> contact_groups MYGROUP
> notification_interval 5
> }
>
> define serviceescalation {
> host_name MYHOST
> service_description Disk Usage
> first_notification 3
> last_notification 0
> contact_groups MYGROUP
> notification_interval 0
> }
>
Are those two actually for the same service on the same host, or is that
just the same placeholder for two different services?
> I'd expect the escalation to notify MYGROUP contacts three times at 5
> minute intervals when my service is in CRITICAL state. After the third
> notification it should stop sending out notifications.
>
notification_interval 5
first_notification 0
last_notification 3
I'm not sure what you had in mind with dual escalations, but the above
lines (in a single escalation) should do what you want.
> Unfortunately it goes on sending out notifications until i manually
> acknowledge the problem or disable notifications for the service.
>
That would be the doing of the "last_notification 0" line in the second
escalation.
> Am I missing something?
>
Obviously. Read the docs on escalations. Understand the docs on
escalations. Try the thing I posted up there. If it fails, file a bug
report.
--
Andreas Ericsson andreas.ericsson at op5.se
OP5 AB www.op5.se
Lead Developer
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
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