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

# Comments

All alarms are saved and kept in Aranet Cloud. Alarms history can be found under **HISTORY** tab in **ALARMS** menu. Either by viewing the history in *Timeline* or in *Table* presentation, click on the notification you would like to add a comment:

<div data-with-frame="true"><img src="https://forum.aranet.com/site/assets/files/4422/screenshot_2023-03-15_110731.png" alt="" width="1181"></div>

Select the *History* option and click on *Comment* to add a comment on the selected alarm

<div data-with-frame="true"><img src="https://forum.aranet.com/site/assets/files/4422/image-3.png" alt="" width="1200"></div>

And add the comment that you would like to have in the pop-up window, and click on the *Save* button:

<div data-with-frame="true"><img src="https://forum.aranet.com/site/assets/files/4422/image-4.png" alt="" width="1200"></div>

The comment will be visible on the top side of the window when selecting the alarm, and a symbol will be displayed in the last field of the line of the alarm to indicate it has a comment:

<div data-with-frame="true"><img src="https://forum.aranet.com/site/assets/files/4422/image-5.png" alt="" width="1200"></div>

When downloading the alarms as a **.xlsx** file, the comments will also be displayed there in the last column of the respective alar


---

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