> ## Documentation Index
> Fetch the complete documentation index at: https://docs.elementary-data.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Alerts and Incidents Overview
Alerts and incidents in Elementary are designed to shorten your time to response and time to resolution when data issues occur.
* **Alert -** Notification about an event that indicates a data issue.
* **[Incident](/cloud/features/alerts-and-incidents/incidents) -** A data issue that starts with a single event but can include multiple events grouped together. An incident includes a start time, status, severity, assignee, and end time. Incident alerts are sent when the incident is opened and when it is resolved.
Alerts provide information and context for recipients to quickly triage, prioritize and resolve issues.
For collaboration and promoting ownership, alerts include owners and tags.
You can create distribution rules to route alerts to the relevant people and channels, for faster response.
An alert would either open a new incident, or be automatically grouped and added to an ongoing incident.
From the alert itself, you can update the status and assignee of an incident. In the [incidents page](/cloud/features/alerts-and-incidents/incidents),
you will be able to track all open and historical incidents, and get metrics on the quality of your response.
## Alerts & incidents core functionality
* **Alerts customization** - Alerts should include relevant context for quick triage such as **owner**, **tags**, **description**. In Elementary, alerts can be customized to include this information.
* **Alert distribution rules** - Alerts should be sent to relevant recipients. By creating [Alert Rules](/cloud/features/alerts-and-incidents/alert-rules), alerts can be distributed to different channels and systems.
* **Incidents management** - When alerts are distributed to different channels, it can become hard to track what is open. Elementary offers a centralized [Incidents page](/cloud/features/alerts-and-incidents/incidents) to monitor what is open, and manage incident properties: **assignee**, **status** and **severity**.
* **[Incident merging](/cloud/features/alerts-and-incidents/incident-merging)** - Merge related incidents manually, let the AI agent suggest merges by root cause, or configure auto-merge rules to group incidents automatically. This reduces noise and helps your team focus on root causes instead of individual symptoms.
* **Automated resolution** - When all monitors in an incident pass again, Elementary automatically resolves the incident, keeping the state of incidents up to date in real time.
* **Mute test alerts** – Mute your test from the test configuration tab to run tests without triggering alerts, giving you more control over notifications while still monitoring data quality. This is useful when testing new data sets, refining thresholds, or adjusting test logic without unnecessary noise.
## Alert types
Elementary can be configured to send alerts on:
* Model run failures
* Failures and/or warnings of dbt tests (including Elementary dbt package and other packages)
* Failures and/or warnings Elementary Anomaly Detection monitors
* Failures and/or warning of custom SQL tests
* dbt source freshness failures
## Supported alert integrations
}
/>
}
/>
}
/>
}
/>
}
/>
}
/>
}
/>
}
/>
