> 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="https://2831658296-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRKwQxnS51pLI9fOl4xXp%2Fuploads%2FI6WCn6L8tnf4j76fcfyx%2Fimage.png?alt=media&amp;token=e80eaf8d-a6d6-4829-92cf-d432818682e5" 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.aranet.com/aranet-cloud-page/aranet-cloud-landing-page/user-interface-and-core-features/alarms.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.