> For the complete documentation index, see [llms.txt](https://docs.itoc360.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.itoc360.com/incidents-and-alerts/alerts.md).

# Alerts

This screen is designed for high observability, allowing your team to quickly identify, prioritize, and respond to critical issues across your infrastructure.

#### The Alert List

The main dashboard displays a grid of all active and historical alerts. Here is a breakdown of the information provided in each column:

* **Provider:** Indicates the technology ecosystem the alert originated from (e.g., Zabbix, Grafana). This helps in quickly identifying the layer of the stack affected.
* **Source:** The specific user-defined integration name (configured in the ***Sources*** section). This tells you exactly which server group, region, or environment sent the alert (e.g., "Prod-DB-Cluster-01").
* **Alert:** The core message or title of the incident. This text is typically parsed from the monitoring payload to show the most relevant error description.
* **Severity:** A visual indicator of urgency (e.g., `Critical`, `Warning`, `Info`). Use this to prioritize which fires to put out first.
* **Status:** The current lifecycle state of the alert (e.g., `Firing`, `Acknowledged`, `Resolved`). This status updates in real-time as the system processes the event or as engineers take action.
* **Created At:** The exact timestamp when the alert was received by ITOC360.

#### Working with Alerts

**1. Triage & Prioritization:** Use the **Severity** column to sort the grid. High-severity incidents (like "Disaster" or "Critical") are typically highlighted to grab immediate attention.

**2. Alert Details:** Clicking on any row in the list will open the Alert Detail View.

**3. Filtering:** You can filter the list by Status to focus only on "Active" issues, removing the noise of resolved incidents from your immediate view.


---

# 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.itoc360.com/incidents-and-alerts/alerts.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.