> For the complete documentation index, see [llms.txt](https://docs.bluerock.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bluerock.io/bluerock-documentation-2.7.0-beta/bluerock-dashboard/alerts.md).
# Alerts
### Overview
The **Alerts** page provides a centralized view of alerts generated in the BlueRock environment. Use it to review alert severity, inspect alert details, and filter alerts by status, severity, type, or time.
The page organizes alerts into three status tabs:
* **Open** — Displays open alerts.
* **Acknowledged** — Displays acknowledged alerts.
* **Dismissed** — Displays dismissed alerts.
The count displayed next to each tab indicates the number of alerts in that status.
***
### Search and Filters
Use the search field and filters above the alert table to narrow the displayed results.
| Control | Description |
| ------------------ | ------------------------------------------ |
| **Search** | Search for an alert, type, host, or agent. |
| **All severities** | Filter alerts by severity. |
| **All types** | Filter alerts by alert type. |
| **Any Time** | Filter alerts by time. |
The alert count shown above the table reflects the results displayed for the current view and filters.
***
### Alert Table
The alert table provides the following information:
| Column | Description |
| --------------- | ------------------------------------------------------------- |
| **Severity** | Severity assigned to the alert, such as Info or Medium. |
| **Alert** | Alert message describing the detected condition. |
| **Type** | Category or type of alert. |
| **Host** | Host associated with the alert, when available. |
| **Raised for** | Entity or resource associated with the alert, when available. |
| **Occurrences** | Number of occurrences displayed for the alert. |
| **First seen** | Time when the alert was first observed. |
| **Last seen** | Time when the alert was most recently observed. |
| **Actions** | Available actions for the alert. |
An alert message may include details about the detected condition, such as a threshold that was exceeded or a change in observed activity.
Use the occurrence count and first-seen and last-seen values to understand how frequently an alert has appeared and when it was observed.
***
### Reviewing Alerts
1. Open **Alerts** from the left navigation.
2. Select **Open**, **Acknowledged**, or **Dismissed** to view alerts by status.
3. Use search or the available filters to narrow the list.
4. Review the alert message, severity, type, associated host or entity, occurrence count, and timestamps.
5. Open the row's **Actions** menu to view the actions available for that alert.
Available actions may depend on the alert's current status and the options provided by the UI.
***
### Interpreting Alert Information
* **Severity** indicates the severity assigned to the alert; it is distinct from the alert's status.
* **Occurrences** indicates the number of occurrences displayed for an alert.
* **First seen** and **Last seen** indicate when the alert was first and most recently observed.
* A dash (—) indicates that the corresponding value is not displayed in the table.
* Use the status tabs to distinguish open alerts from acknowledged and dismissed alerts.
***
---
# 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.bluerock.io/bluerock-documentation-2.7.0-beta/bluerock-dashboard/alerts.md?ask=&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.
.png)
