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

# Alerts & Notifications | OpenMetadata Guide

> Configure alerts and notifications for data observability and system governance events across your data catalog.

# Alerts & Notifications

OpenMetadata has been providing observability alerts right from the start to notify users of important data lifecycle events: schema modifications, ownership shifts, and tagging updates. Users can define fine-grained alerts and notifications.

Starting from the 1.3 release, Data Observability alerts have been completely revamped, simplifying the process of monitoring data. Users can quickly create alerts for:

* **Changes in the Metadata:** such as schema changes,
* **Data Quality Failures:** to filter by Test Suite,
* **Pipeline Status Failures:** when ingesting runs from your ETL systems, and
* **Ingestion Pipeline Monitoring:** for OpenMetadata’s ingestion workflows

Depending on your use cases, notifications can be sent to owners, admins, teams, or users, providing a more personalized and informed experience. Teams can configure their dedicated Slack, MS Teams, or Google Chat channels to receive notifications related to their data assets, streamlining communication and collaboration. With the alerts and notifications in OpenMetadata, users can send Announcements over email, Slack, or Teams. Alerts are sent to a user when they are mentioned in a task or an activity feed.

[YouTube video player](https://www.youtube.com/embed/0QlFSIovjOQ?si=QgwxJO-UrCWBR1Ab)

## Observability Alerts & Notifications

OpenMetadata provides a unified **Event Subscription** framework that allows you to configure alerts for two main purposes:

1. **Data Observability:** Monitoring the health of data systems (e.g., Data Quality failures, Schema Drift, Pipeline failures).
2. **System & Governance Notifications:** Monitoring metadata changes and collaboration events (e.g., new Glossary terms, Tag updates, Ownership changes).

While these alerts serve different use cases and are accessed from different menus within the platform, the configuration process follows a similar workflow.

### Required Permissions

> [card] [Required Permissions](https://docs.open-metadata.org/v2.0.x/how-to-guides/admin-guide/roles-policies.md)
>
> Setting up alerts and notifications requires **Create** permission on the `EventSubscription` entity.

### Configuration Workflow

Select your use case below to see the specific configuration steps:

> [card] [Data Observability Alerts](https://docs.open-metadata.org/v2.0.x/how-to-guides/data-quality-observability/alerts-notifications/data-observability-alerts.md)
>
> Monitor the health of your data systems with alerts for pipeline failures, data quality issues, and schema changes.

> [card] [System & Governance Notifications](https://docs.open-metadata.org/v2.0.x/how-to-guides/data-quality-observability/alerts-notifications/system-governance-notifications.md)
>
> Stay informed about metadata changes, governance events, and collaboration activities across your data catalog.

### Additional Details for the Configuration of External Destinations

OpenMetadata supports multiple external destinations for delivering alerts outside the platform. Each destination type requires a specific setup process.

> [card] [Email](https://docs.open-metadata.org/v2.0.x/how-to-guides/data-quality-observability/alerts-notifications/email-alerts-configuration.md)
>
> Send alerts directly to recipient email addresses using your OpenMetadata server’s email configuration.

> [card] [Slack](https://docs.open-metadata.org/v2.0.x/how-to-guides/data-quality-observability/alerts-notifications/slack-alerts-configuration.md)
>
> Deliver alerts to Slack channels using Incoming Webhooks.

> [card] [Microsoft Teams](https://docs.open-metadata.org/v2.0.x/how-to-guides/data-quality-observability/alerts-notifications/microsoft-teams-alerts-configuration.md)
>
> Post alerts to Teams channels using Workflow Webhooks with Adaptive Cards.

> [card] [Google Chat](https://docs.open-metadata.org/v2.0.x/how-to-guides/data-quality-observability/alerts-notifications/google-chat-alerts-configuration.md)
>
> Send alerts to Google Chat Spaces using Webhooks.

> [card] [Generic Webhook](https://docs.open-metadata.org/v2.0.x/how-to-guides/data-quality-observability/alerts-notifications/generic-webhook-alerts-configuration.md)
>
> Integrate with custom applications using generic webhooks.

### Reference

> [card] [Alert Behavior Reference](https://docs.open-metadata.org/v2.0.x/how-to-guides/data-quality-observability/alerts-notifications/alert-behavior-reference.md)
>
> Sources, triggers, and filters for each alert type, when alerts fire, and which alert covers incidents.

> [card] [Webhook Payloads and Delivery](https://docs.open-metadata.org/v2.0.x/how-to-guides/data-quality-observability/alerts-notifications/webhook-payloads-and-delivery.md)
>
> Payload examples, authentication, failure handling, duplicates, and ordering.

> [card] [Alerts API](https://docs.open-metadata.org/v2.0.x/api-reference/alerts.md)
>
> Create and manage alerts with the REST API and Python SDK.

> [card] [Incidents API](https://docs.open-metadata.org/v2.0.x/api-reference/incidents.md)
>
> List incidents and change their status through the API.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.