> 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/documentation/widgets/benutzerdefinierte-widgets/module/alarm.md).
# Alarm
The *Alarm Widget* in Eliona, it allows alarms for a specific asset or a list of alarms to be displayed and managed. This can be used both for individual assets and for an overview of all alarms.
[A]
Description
This text is displayed when the custom widget is later connected to assets
[B]
Variant
This option is only available when Alarm type [C] ""Total number of alarms" is selected
Large: Shows how many tickets there are in total
Small: Displays the tickets sorted only by categories.
[C]
Alarm type
Total number of alarms: Displays all existing alarms sorted by priority. -> to the widget
Alarm for asset: Displays all alarms for a single asset. -> to the widget
List of alarms: Displays all alarms in a scrollable list. -> to the widget
Detailed list of alarms: Displays the alarms in detailed form. -> to the widget
---
# 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/documentation/widgets/benutzerdefinierte-widgets/module/alarm.md?ask=&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.
