> For the complete documentation index, see [llms.txt](https://docs.twtg.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.twtg.io/docs/solidred-documentation/solidred-3.3/data-analytics-features/alerts.md).
# Alerts
Alerts are indications from SolidRed based on the NEON devices' input to indicate situations where the end-user should check the device or the asset being monitored. The alerts in SolidRed are divided into 2 categories:
* **Machine alerts:** alerts based on or from the device's data that indicate a situation with the monitored machine or asset. Machine alerts have common alerts across all use cases (e.g., device condition alerts that report on thresholds set in the configuration of the device) and use-case-specific alerts, such as machine fault alerts in the case of the vibration use cases and steam trap alerts in the case of the steam line use cases.
* **Device alerts:** alerts about the health of the device, such as signal strength, battery level, or inactivity. Most device alerts are common across use cases; however, some are device-specific.
On the any alerts table, the user can interact with the alerts as follows:
* Clicking on the alert will display a pop-up window with further details about the alert.
* Clicking on the message icon allows the user to see, add, and edit comments to the alert.
* Clicking on the checkmark will acknowledge the alert.
* Clicking on the **X** will clear the alert. Alerts are automatically cleared if the sensor reports a healthy state on the following message related to the alert.
Alerts table example
---
# 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://docs.twtg.io/docs/solidred-documentation/solidred-3.3/data-analytics-features/alerts.md?ask=&goal=
```
`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.