> For the complete documentation index, see [llms.txt](https://help.boomerang3.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.boomerang3.com/boomerang-3-domain-administrator-manual/dashboard/alarms_and_warnings.md).

# Alarms and warnings handling

Boomerang system may observe if a reading from a given measuring point is within its predefined range and raise an alarm if the value is outside the limits. 

The limits may be defined as alarms or warnings as described in [Alarm Limits](/boomerang-3-domain-administrator-manual/admin/alarms/alarms__alarm_limits.md). In this chapter term "Alarm" is used but all the descriptions below are also true for warnings.

The alarms and warnings handling is presented below.

{% stepper %}
{% step %}

### Alarm is triggered

An active alarm is generated in the system basing on the [Alarm Limits](/boomerang-3-domain-administrator-manual/admin/alarms/alarms__alarm_limits.md) and [Alarm filter](/boomerang-3-domain-administrator-manual/dashboard/alarms_and_warnings/alarm-filter.md). The communication alarms are activated basing on communication filter setting as described in [Alarm types](/boomerang-3-domain-administrator-manual/dashboard/alarms_and_warnings/alarm-types.md).

The alarms are shown in the system as described in [Alarm presentation](/boomerang-3-domain-administrator-manual/dashboard/alarms_and_warnings/alarm-presentation.md) .
{% endstep %}

{% step %}

### Alarm is delivered to user(s)

The alarm message is delivered to the user as presented in [Alarm delivery](/boomerang-3-domain-administrator-manual/dashboard/alarms_and_warnings/alarm-delivery.md).
{% endstep %}

{% step %}

### Correcting and preventing actions

User checks the alarm cause in the system using [Alarm presentation](/boomerang-3-domain-administrator-manual/dashboard/alarms_and_warnings/alarm-presentation.md) and makes corrections. At the end of this step, depending on the [Alarm types](/boomerang-3-domain-administrator-manual/dashboard/alarms_and_warnings/alarm-types.md), the values must be  back within the limits or communication with the MP must be restored.

It is always important to perform also preventing actions that will reduce the risk, the same problem will appear again.
{% endstep %}

{% step %}

### Alarm is signed

The alarm is signed confirming it was handled properly and can be inactivated. After signing, the alarm is closed and is only visible in the history. It is recommended to add a comment that describes the alarm cause when signing.

A warning is signed by the system itself when the cause of the warning disappears e.g. after the value is back within the warning limits.

{% hint style="danger" %}
If the condition that caused the alarm is still valid after signing, then the alarm will be triggered again.
{% endhint %}
{% endstep %}
{% endstepper %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.boomerang3.com/boomerang-3-domain-administrator-manual/dashboard/alarms_and_warnings.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.