> 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/platform/alert-center/alarms/alarm-statistics.md).

# Alarm Statistics

The *Alarm Statistics* provides a comprehensive analysis of all alarms that have occurred in a tenant. It allows for a detailed evaluation of alarms by frequency, duration, and severity. This helps to recognize patterns, identify problem sources, and take targeted measures to improve system stability.

In the statistics, various charts and tables can be viewed, including:

* **Alarm distribution by severity** (e.g., High, Medium, Low, Info)
* **Weekly overview** of alarms
* **Alarm heatmap**, which visualizes the distribution of alarms over a period of time
* **Alarm frequency**, which shows which assets trigger alarms most often
* **Alarm duration**, which indicates how long an alarm was active at a time

<div data-full-width="true"><figure><img src="https://3489494878-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9GvUpaatBiReR43XFSMg%2Fuploads%2F74OuipnLpNQuiunNnFpg%2FAlarm%20statistik%20(1).png?alt=media&#x26;token=c5195897-6600-439e-98ff-193ea98d739f" alt=""><figcaption></figcaption></figure></div>

### Filter Options

1. Select the tags in **\[A]**.
2. Select **All the selected required** or **One of the selected** in **\[A]** to combine the selected tags.\
   ◈ **All the selected required** uses AND logic. **One of the selected** uses OR logic.
3. Set the time period in **\[B]**—e.g., the last 7 days, a custom period, or fixed dates.\
   ◈ This makes it easier to recognize trends or accumulations within specific time windows.
4. Click **Apply** **\[C]** to activate the selected tags and time period.\
   ▷ The view is immediately updated with the new filter criteria.

Click **Reset** **\[D]** to clear the selected tags and restore the default time period.

### Choose AND or OR

| Mode                                | When to use it                                             | Example                                                                                                     |
| ----------------------------------- | ---------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------- |
| **All the selected required** (AND) | Narrow the analysis to alarms matching every selected tag. | Select `Building A` and `Ventilation` to focus on ventilation alarms associated with Building A.            |
| **One of the selected** (OR)        | Include alternatives in one analysis.                      | Select `Building A` and `Building B` to include alarms matching either tag, including alarms matching both. |

With one selected tag, both modes return the same matches. With no tags selected, tags do not restrict the analysis. The selected time period still applies.

For information about creating and assigning tags, see [Tags](/collection/mandatory-base/platform-core/workspace-and-identity/tags.md).


---

# 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/platform/alert-center/alarms/alarm-statistics.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.