Introduction
Shinken supports optional escalation of contact notifications for hosts and checks. Escalation of host and check notifications is accomplished by defining escalation objects Escalation.
When Are Notifications Escalated?
...
Look at the example below:
| Property | Value |
|---|---|
| Name | To-level-2 |
| first_notification_time | 60 |
| last_notification_time | 120 |
| contact_groups | nt-admins,managers |
It will use the interval length for the value you set for first/last notification time. Here, it will escalate after 1 hour problem, and stop at 2 hours.
...
When defining notification escalations, it is important to keep in mind that any contact groups that were members of "lower" escalations (i.e. those with lower notification time ranges) should also be included in "higher" escalation definitions. This should be done to ensure that anyone who gets notified of a problem continues to get notified as the problem is escalated.
Example:
| Property | Value |
|---|---|
| Name | To-level-2 |
| first_notification_time | 60 |
| last_notification_time | 120 |
| contact_groups | nt-admins,managers |
| Property | Value |
|---|---|
| Name | To-everyone |
| first_notification_time | 120 |
| last_notification_time | 240 |
| contact_groups | nt-admins,managers,everyone |
...
The first (or "lowest") escalation level includes both the nt-admins and managers contact groups. The last (or "highest") escalation level includes the nt-admins, managers, and everyone contact groups.
...
Notification escalation definitions can have notification ranges that overlap. Take the following example:
| Property | Value |
|---|---|
| Name | To-level-2 |
| first_notification_time | 60 |
| last_notification_time | 240 |
| contact_groups | nt-admins,managers |
| Property | Value |
|---|---|
| Name | To-everyone |
| first_notification_time | 120 |
| last_notification_time | 0 |
| contact_groups | on-call-support |
...
In the example above:
- The nt-admins and managers contact groups get notified on between 1 and 2 hours
...
- Only the on-call-support contact group gets notified after 4 hours
...
Escalations based on time short time
...
Let take an example :
Host:
| Property | Value |
|---|---|
| Name | srv-important |
| notification interval | 1440 |
| escalations | To-level-2 |
Then with the escalations object:
| Property | Value |
|---|---|
| Name | To-level-2 |
| first_notification_time | 60 |
| last_notification_time | 120 |
| contact groups | level2 |
Here let say you have a problem HARD on the check at t=0. It will notify the host contacts. The next notification should be at t=1440 minutes, so tomorrow. It's ok for classic notifications, but not for escalated ones.
...
So you can put large notification_interval and still have quick escalations times.
Time Period Restrictions
Under normal circumstances, escalations can be used at any time that a notification could normally be sent out for the host or check.
...
If you would like to restrict the escalation definition so that it is only used when the host or check is in a particular state, you can use the scalation options directive in the escalation definition. If you do not use the "escalation_options" directive, the escalation can be used when the host or check is in any state.