> For the complete documentation index, see [llms.txt](https://docs.buildings.ability.abb/collection/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.buildings.ability.abb/collection/english-v14/getting-started/4.-daten-visualisieren-and-nutzen/einen-alarm-konfigurieren.md).

# Configure an alarm

To configure an alarm, you must create a rule. When the conditions of this rule are met (e.g., temperature rises above 25 ºC), an alarm is created.

{% hint style="info" %}
The full documentation can be found in the chapter [↗ Alarms, Rules, Escalations](/collection/english-v14/documentation/alarme-regeln-und-eskalationen.md)
{% endhint %}

<figure><img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/WwSSu8PReXgB6OmF0z0C/Docs%20-%20Regeln_2%20v2.png" alt=""><figcaption></figcaption></figure>

1. Click on **RULES \[A]**\
   ▷ The rule overview opens
2. Click on **\[B]**\
   ▷ The window **Add rules \[C]** opens
3. Enter in **\[F]** the asset to which the rule refers.
4. Enter in **\[G]** the type of alarm.
5. Enter in **\[H]** the attribute to which the rule refers.
6. Enter in **\[I]** and **\[I1]** the condition that must be met for an alarm to be triggered.
7. Enter in **\[J]** which priority an alarm triggered by this rule will have.
8. Enter in **\[K]** whether an alarm triggered by this rule must be acknowledged.
9. Optional: Assign the rule in **\[L]** one or more tags.
10. Configure in **\[M]** which message should appear when the alarm is triggered.
11. Click Add rule **\[O]**, to create the rule.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.buildings.ability.abb/collection/english-v14/getting-started/4.-daten-visualisieren-and-nutzen/einen-alarm-konfigurieren.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.