> 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/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.  &#x20;
* **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.&#x20;

Alerts are displayed on:

* Events center: main location of alarms where all of them are listed. Further details available in the [Events Center](https://docs.twtg.io/docs/solidred-documentation/common-dashboards/events-center.md) section.
* Entities hierarchy: entities with alarms are tagged as explained in the [Navigation Panel](https://docs.twtg.io/docs/solidred-documentation/getting-started/navigation-panel.md) section.
* Detail dashboard: displayed in the Health widget of the detail dashbaord.


---

# 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://docs.twtg.io/docs/solidred-documentation/features/alerts.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.
