Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Introduction

 

Shinken supports optional escalation of contact notifications for hosts and checks. Escalation of host and check notifications is accomplished by defining escalation objects.

When Are Notifications Escalated?

Notifications are escalated if and only if one or more escalation definitions matches the current notification that is being sent out. If a host or check notification does not have any valid escalation definitions that applies to it, the contact group(s) specified in either the host group or check definition will be used for the notification.

Look at the example below:

Enterprise permet en option de définir des niveaux d'escalade sur les contacts. Cette option est activée dans "escalation objects."

Quand les notifications sont-elles escaladées ?

Les notifications sont escaladées si et seulement si une ou plusieurs définitions d'escalade correspondent à la notification qui est envoyée . Si un hôte ou une notification n'a pas de définitions d'escalade valides qui s'y applique , le groupe ( s) de contact spécifié dans le groupe d'hôtes ou le service sera utilisée pour la notification .

Voyons un exemple:

PropriétéValeurPropertyValue
NameTo-level-2
first_notification_time60
last_notification_time120
contact_groupsnt-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.

Contact Groups

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:

Il utilisera la valeur d'intervalle de temps défini pour la 1ère/dernière notification.Dans cet exemple, il escaladera 1 heure après le problème,et s'arrêtera 2 heures après. 

Groupes de contacts

Lorsqu'on définit les escalades de notifications, il est important de garder à l'esprit qu'il faut inclure dans la définition la plus haute tous les contacts qui étaient en définition la plus basse. Cela permet de garantir que tout le monde continuera d'être prévenu en cas d'escalade. 

 

Exemple:

PropriétéValeurPropertyValue
NameTo-level-2
first_notification_time60
last_notification_time120
contact_groupsnt-admins,managers
PropertyPropriétéValueValeur
NameTo-everyone
first_notification_time120
last_notification_time240
contact_groupsnt-admins,managers,everyone

 


The first (or "lowest") escalation level includes both the Le 1er niveau (ou "le plus bas") comprend à la fois le groupe nt-admins and et les managers contact groups. The last (or "highest") escalation level includes the .Le dernier niveau (ou "le plus élevé") comprend le groupe nt-admins, les managers, and everyone contact groups.Notice that the nt-admins contact group is included in both escalation definitions. This is done so that they continue to get paged if there are still problems after the first two check notifications are sent out. The managers contact group first appears in the "lower" escalation definition - they are first notified when the third problem notification gets sent out. We want the managers group to continue to be notified if the problem continues past five notifications, so they are also included in the "higher" escalation definition.et tout le monde dans le groupe. 

Notez que le groupe de contacts nt-admins est défini dans les 2 niveaux d'escalade. Cela leur permet de continuer d'être avertis si il y a toujours un problème après que les 2 premières notifications ont été envoyées. Idem pour le groupe de contacts "managers", qui doivent continuer d'être avertis également.  

Overlapping Escalation Ranges

Notification escalation definitions can have notification ranges that overlap. Take the following example:

...

  • Only the on-call-support contact group gets notified after 4 hours

 

Escalations based on time short time

It's also interesting to see that with escalation based on time, if the notification interval is longer than the next escalation time, it's this last value that will be taken into account.

...

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.

...

Escalated notifications are still subject to the normal time restrictions imposed by the "notification_period" directive in a host or check definition, so the timeperiod you specify in an escalation definition should be a subset of that larger "notification time window".

State Restrictions

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.

...