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

# Alarm History

The **Alarm History** tab provides a detailed log of all alarm events that have occurred in the workspace. It allows users to review past alarm activity, understand when and why alarms were triggered, and track how long each alarm remained active.

In the Alarm History tab, you can:

* View a chronological list of all alarm activations
* See timestamps for when alarms were triggered and resolved
* Identify the sensor or virtual sensor associated with each alarm
* Review status changes
* Filter and search historical alarm records for easier analysis

Alarm History is useful for reporting, as it ensures full visibility into sensor behavior and environment alarm-related events over time.

There are two trendline view types:

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

<div data-with-frame="true"><figure><img src="/files/WGN44fAO5HPIzHWmN2y4" 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 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/alarm-history.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.