Hi All … we have nagios 2.9 running with 3 escalations level …
- second line support
- third line support
- all engineers.
What seems to happen is that if a service/host is in a warning state for a while, and then goes to critical, it directly escalates to the step ‘3’ - all engineers.
Which seems to annoy people who wake up with a sms
So is this a bug or a feature Or did I configure something wrong … Escalation definitions are blow … I’d
love to know how to ignore the ‘warnings’ in the notification counters.
[code]define hostescalation {
host_name .*
contact_groups level_1
first_notification 3
last_notification 0
notification_interval 10
escalation_options d,u,r
}
define hostescalation {
host_name .*
contact_groups level_1,level_2
first_notification 6
last_notification 0
notification_interval 10
escalation_options d,u,r
}
define hostescalation {
host_name .*
contact_groups level_1,level_2,level_3
first_notification 9
last_notification 0
notification_interval 10
escalation_options d,u,r
}
define serviceescalation {
host_name .*
service_description .*
contact_groups level_1
first_notification 3
last_notification 0
notification_interval 10
escalation_options c,u,r
}
define serviceescalation {
host_name .*
service_description .*
contact_groups level_1,level_2
first_notification 6
last_notification 0
notification_interval 10
escalation_options c,u,r
}
define serviceescalation {
host_name .*
service_description .*
contact_groups level_1,level_2,level_3
first_notification 9
last_notification 0
notification_interval 10
escalation_options c,u,r
}[/code]