> 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/admin/alarms/alarms__alarm_limits.md).

# Alarm Limits

Alarms are defined using Alarm Limits and Alarm Groups located in Admin – Alarms.

An Alarm Limit is a definition of a low and/or high limit value and is a source of an alarm. If the measurement is beyond the limit, then an alarm is activated.

If both high and low limit values are defined, then the alarm is activated if the measurement is lower than the low limit or higher than the high limit. If only one of the limits is defined, then the measurements beyond this value activate an alarm.

The limits have a parameter that defines their sensitivity, described in [Alarm filter](/boomerang-3-domain-administrator-manual/dashboard/alarms_and_warnings/alarm-filter.md) chapter.

The Alarm Limit can be defined as a Warning or as an Alarm.

A Warning deactivates an alarm when the readings are back to normal automatically. In case of an Alarm, a user must sign the alarm activated, it will not be deactivated automatically.

The Alarm Limits available are shown and can be selected in the Measuring Point settings.


---

# 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://help.boomerang3.com/boomerang-3-domain-administrator-manual/admin/alarms/alarms__alarm_limits.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.