Hi All ...
we have nagios 2.9 running with 3 escalations level ...
1) second line support
2) third line support
3) 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: Select all
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
}
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Nagios-users mailing list
Nagios-users@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
