> 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/rules.md).

# Rules

The **Rules** tab allows you to automate actions in Aranet Cloud based on predefined conditions. Rules continuously monitor sensor and system events and automatically trigger selected actions when specific criteria are met, reducing the need for manual supervision.

<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%2F3ieyJeyOtkqf7T4B9klT%2Fimage.png?alt=media&amp;token=1f0fa5d3-2103-4ce7-a3dc-ec56a82caa2a" alt=""><figcaption></figcaption></figure></div>

In this section, you can create and manage rules that respond to events such as alarm state changes, sensor thresholds being exceeded, or other system conditions. Rules help streamline workflows and ensure consistent reactions to important events.

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

* Create automation rules based on alarms or sensor events
* Define conditions that trigger rule execution
* Configure automatic actions, such as notifications or system responses
* Enable or disable rules as required
* Review and edit existing rules

Rules enhance operational efficiency by enabling proactive, automated responses to critical events, helping maintain reliability and control across your monitored environment.

Here is how you can create an Alarm Rule:

<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%2F4yheRR4aK7zY4KEtYfa1%2F1215-ezgif.com-video-to-gif-converter.gif?alt=media&amp;token=3dae0650-362c-45fa-9e40-c13e46e82446" alt=""><figcaption></figcaption></figure></div>

By pressing on the Alarm Rule, you can access information about active alarms, linked sensors and thresholds.

<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%2FPC4CecKxyR9pcrngXCVT%2Fimage.png?alt=media&amp;token=e7eba775-aff9-4bef-8d9b-144d504bb938" alt=""><figcaption></figcaption></figure></div>


---

# 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/rules.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.