# Group escalations

## Overview

If many alarms are triggered within a short period of time, this can lead to a flood of notifications. To avoid this, alarms can be combined within an escalation. In this process, several incoming alarms are consolidated into a single escalation message, depending on individually defined conditions. In addition, certain alarm tags can be excluded from the combination, so that these continue to be escalated individually.

### Procedure

<div data-full-width="true"><figure><img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/cJAnmBzH9WzDO1JqlUll/Eskalation%20(2).png" alt=""><figcaption></figcaption></figure></div>

1. Click on *Engineering* **\[A]**
2. Click on *escalation* **\[B]**

   ▷ The overview of the escalation configurations opens.
3. Click on **\[D]**\
   ▷ The window opens *Combining alarms* **\[D1]**.
4. Activate the switch **\[D2]**, to activate the combining of alarms.
5. Enter under **\[D3]** the period in seconds within which the alarms must occur in order to be combined.
6. Enter under **\[D4]** the minimum number of alarms that must occur within the defined period for them to be combined.
7. Select under **\[D5]** the alarm tags that should be excluded from the combination (e.g. *High Prio*).
8. Click on **Save** **\[D6]**, to apply the changes.

### Example

**Conditions:**

* Period: **10 seconds**
* Minimum number: **5 alarms**

**Scenario 1:**\
Within 8 seconds, 5 alarms are triggered without excluded tags → **The alarms are combined** and sent as a single escalation message.

**Scenario 2:**\
Within 10 seconds, 4 alarms are triggered → **No combination**, 4 separate escalation messages are sent.

**Scenario 3:**\
Within 10 seconds, 7 alarms are triggered, 2 of them with the tag *High Prio* (excluded) → The 5 remaining alarms are combined, the 2 *High Prio*-alarms are escalated individually.
