> For the complete documentation index, see [llms.txt](https://help.aranet.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.aranet.com/aranet-cloud-page/aranet-cloud-landing-page/user-interface-and-core-features/alarms.md).

# Alarms

The **Alarms** tab allows you to receive notifications when predefined conditions are met. Alarms help ensure that critical environmental parameters remain within acceptable limits and enable fast response to potential issues.

<div data-with-frame="true"><figure><img src="/files/C94hHi1iZyIumBdKiSQJ" alt=""><figcaption></figcaption></figure></div>

In this section, you can create, view, and manage alarms based on measurements from physical and virtual sensors. Each alarm is triggered when sensor values exceed or fall below defined thresholds for a specified duration. Alarm status and history are continuously updated and visible in the system.

Using the **Alarms** tab, you can:

* Create alarms for individual sensors or virtual sensors
* Define upper and lower threshold values
* Configure delay times to avoid false alarms
* Enable or disable alarms as needed
* Review active and historical alarms

Alarms provide proactive monitoring and help maintain safety, quality, and compliance across all monitored environments by ensuring that important changes are detected immediately.


---

# 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, and the optional `goal` query parameter:

```
GET https://help.aranet.com/aranet-cloud-page/aranet-cloud-landing-page/user-interface-and-core-features/alarms.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.