> ## Documentation Index
> Fetch the complete documentation index at: https://docs.drdroid.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Alerts Inbox

The **Alerts Inbox** is your central dashboard for viewing and managing alerts generated from multiple sources such as monitoring tools, bots, and internal systems. It helps on-call engineers prioritize and debug issues quickly by surfacing actionable alerts in a unified view.

It has all the alerts you have received on Slack in different channels where you have added @drdroid.

| Column        | Description                                                                                                                                                                                                                                                                                                                                   |
| :------------ | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Title**     | Alert message or headline. It includes a clickable link to the alert detail page.                                                                                                                                                                                                                                                             |
| **Severity**  | Indicates urgency. Examples: `Critical`, `Warning`, `Info`, `Unspecified`, or icons/colors. Helps prioritize response.                                                                                                                                                                                                                        |
| **Status**    | Lifecycle stage of the alert:• `New` – Not yet handled• `Acknowledged` – Someone has just started working on it• `Triaged` – Someone has debugged the alert• `Escalated` – It has been escaled to the senior engineer• `Remediated/Resolved` – The issue has been resolved permanently or temporarily• `Hidden` – Manually snoozed or ignored |
| **Type**      | Origin system for the alert (e.g., `Rollbar`, `custom_bot`, `hipctl`).                                                                                                                                                                                                                                                                        |
| **Channel**   | Slack channel of the alert (`#logs`, `#monitoring`, etc.).                                                                                                                                                                                                                                                                                    |
| **Timestamp** | When the alert was triggered. Useful for time-based debugging.                                                                                                                                                                                                                                                                                |
| **Actions**   | Contextual actions available per alert (explained below).                                                                                                                                                                                                                                                                                     |

### 🎬 Available actions

Each alert row include three actios and mentioned in the following:

| Action                 | Description                                                                                                                                       |
| :--------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------ |
| **🧠 Debug with AI**   | Launches DrDroid’s AI debugger. Automatically runs queries, checks logs/metrics, and generates a possible root cause analysis.                    |
| **📘 Execute Runbook** | Opens a suggested runbook (step-by-step remediation guide) mapped to the alert fingerprint/type. You can run individual tasks or steps.           |
| **👁️ Hide Alert**     | Temporarily removes the alert from active view. Useful for noise suppression or marking duplicates. It may still be accessible in search/history. |

## 💡 Pro Tips

* Prioritize alerts based on **Severity** and **Status**.
* Use **AI Debug** for high-volume or vague alerts—it summarizes findings for you.
* Apply **Channel** and **Type** filters when triaging cross-system incidents.
* Use **Runbook Execution** for known, recurring issues to act faster.

***

What’s Next

* [Alerts Details](/agent/alert-details)