# Create failed event alerts in Console
> Configure email or Slack alerts for failed events with custom filters and thresholds in the data quality dashboard.
> Source: https://docs.snowplow.io/docs/monitoring/alerts/failed-event-alerts/creating-alerts/
> Documentation index: https://docs.snowplow.io/llms.txt

Set up failed event alerts to receive notifications when failed events occur in your data pipeline.

You'll need access to the [data quality dashboard](/docs/monitoring/#data-quality-dashboard).

To create an alert, go to Snowplow Console:

1. Navigate to **Data Quality** in the left sidebar
2. Click **Manage alerts** in the top-right corner
3. Click **Create alert**

![Manage alerts page in an empty state showing \&quot;No alerts added\&quot; and a Create alert button](/assets/images/data_quality_create_alert-afeeedce7f41da59235c86224c07e133.png)

## Configure destination

Choose how you want to receive notifications:

### Email notifications

1. Select **Email** as destination
2. Add recipient email addresses
3. Click **Add filters** to configure filters
4. Configure triggers as needed
5. Enter alert name (e.g., "mobile-app")

![Create alert form with Email selected as the destination, two recipient addresses added, trigger set to \&quot;When above value\&quot; with insights showing 313 failed events per day and a suggested threshold of 626, delivery set to Daily, and the alert named \&quot;web-login\&quot;](/assets/images/data_quality_create_email_alert-ef8f9719550f38c878ee8c23e41e2e62.png)

### Slack notifications

1. Select **Slack** as destination
2. Select Slack channel from dropdown
3. Click **Add filters** to configure filters
4. Configure triggers as needed
5. Enter alert name (e.g., "web-app")

![Create alert form with Slack selected as the destination and the Slack channel dropdown open, listing three channels including #slack-alerts-test](/assets/images/data_quality_create_slack_alert-7ea1342a4fb75fc85430eaf2aa37573c.png)

When no active Slack integration is found, a `Connect with Slack` button will appear instead of the list of channels.

![Destination section showing a \&quot;Connect with Slack\&quot; button, which appears when no active Slack integration is found](/assets/images/data_quality_connect_slack-19cd34be33c56ff687d46d51edee16a4.png)

A Slack consent screen will appear.

![Slack permission screen requesting access for \&quot;Snowplow Notifications\&quot; to view channel content and perform actions in the Snowplow Slack workspace](/assets/images/data_quality_slack-619e081be9bee27143d1b537cda3ec1d.png)

To select channels in the UI, first add the app to those channels. In Slack:

1. Open the channel where you want notifications
2. Type `@Snowplow Notifications` and send
3. Click "Add them" when prompted

![Slackbot message saying \&quot;You mentioned @Snowplow Notifications, but they\&#39;re not in this channel,\&quot; with Add them and Do nothing buttons](/assets/images/data_quality_slack_invite-9dfb992f8c26e95209f7343bf6f215f0.png)

Once a Slack alert is configured you will see a confirmation notification in the selected Slack channel.

![Slack message from Snowplow Notifications confirming a successful integration, showing alert name \&quot;web-login\&quot; and active filters for ResolutionError and ValidationError issue types on the mobile-login data structure](/assets/images/data_quality_slack_confirmation-6bc7271ab78f4dd95a12da4fc7251319.png)

## Set up filters

Configure when alerts should trigger:

1. **Issue types**: select `ValidationError`, `ResolutionError`, or both
2. **Data structures**: choose specific data structures (all versions will apply)
3. **App IDs**: filter by application identifiers

![Filters panel showing ResolutionError and ValidationError selected as issue types, the mobile-login data structure filtered, and no app IDs configured](/assets/images/data_quality_filters-3a3e756dad9c7851f98b9e71d6f72796.png)

## Configure triggers

Set up when alerts should be triggered based on failed event conditions:

### Trigger types

Choose from the available trigger options:

- **When above value**: set an absolute threshold for failed events (e.g., 1,500 failed events per hour)
- **On any new issue**: alert when a new type of failure appears

![Alert trigger type selector with two options: \&quot;When above value\&quot; for setting an absolute failed event threshold, and \&quot;On any new issue\&quot; for alerting when a new failure type appears, with \&quot;On any new issue\&quot; selected](/assets/images/data_quality_trigger_types-b7e111c3416bd0066f6c6a6d5405ec63.png)

### Threshold configuration

When using the **When above value** trigger:

1. **Value**: Enter the threshold number of failed events
2. **Time period**: Select the time window (10 minutes, hour, or day)
3. **Deliver**: Choose notification frequency (daily, weekly, or monthly)

![Alert threshold configuration panel showing Value, Time period, and Deliver fields, alongside an Insights panel with average event volume, a suggested threshold value, and an Apply suggestion button based on the last 7 days of data](/assets/images/data_quality_absolute_threshold-7de6b5f5e3715629c19e2c68b01cdcff.png)

#### Insights from recent data

When configuring a threshold alert, the Insights panel displays data from the last 7 days to help you choose an appropriate threshold:

- **Average events volume** - Shows the average counts of valid and failed events (per relevant time unit)
- **Suggested threshold** - Provides a recommended threshold value based on recent patterns
- **Apply suggestion** - Click to automatically populate the threshold value field with the suggested value

Use these insights to set realistic thresholds that reflect your actual event patterns.

**Alert delivery:** If the trigger condition is met, the alert is sent once per delivery interval you selected.

## Complete setup

1. Review your configuration
2. Click **Confirm** to create the alert
3. Your alert will appear in the alerts list

## Alert frequency

Alerts are checked every 10 minutes. What triggers a notification depends on the trigger type. See [alert behavior](/docs/monitoring/alerts/failed-event-alerts/managing-alerts/#alert-behavior) for details.
