Hello everyone,
My latest nagios related woe is in relation to service escalations.
I have recently found that where I have listed multiple hosts within a single service escalation def, the escalations do not appear to function as they should.
Before I detail the issue, here is a copy of the escalations I have in place for each of my service defs:
define serviceescalation {
host_name ,,…
service_description <srv_desc>
first_notification 1
last_notification 0
contact_groups admins
notification_interval 20
escalation_period workhours
}
define serviceescalation {
host_name ,,…
service_description <srv_desc>
first_notification 1
last_notification 0
contact_groups support_primary
notification_interval 20
}
define serviceescalation {
host_name ,,…
service_description <srv_desc>
first_notification 2
last_notification 0
contact_groups support_shadow
notification_interval 20
}
For each service escalation definitions that list multple hosts, the alert notifications recevied by the support_shadow contact group are very erratic. Sometimes this group receives the 1st notification, other times the 2nd (as intended), sometimes they receive the recovery notification having not received a critical notification - it appears to be quite random.
Admittedly, I probably don’t require the 2nd escalation definition that is listed above, yet I don’t believe this configuration would cause any problems to occur either, especially since I do not experience this issue for any of the numerous escalation defs that have just a single host defined.
I am aware that I can use the host_groups parameter to avoid listing multiple hosts, but for various reasons, this is not something I can deploy right now, besdies that would only be a workaround and not a fix.
Can anybody confirm whether they have a configuration similar to my own which works? Or do any of you have ay pointers? I’ve been through the documentation and can’t find any information which helps.
Thanks!