Skip to main content

Setting up alerts on Dagster+

Dagster+ allows you to configure alerts to automatically fire in response to a range of events. These alerts can be sent to a variety of different services, depending on your organization's needs.

These alerts can be configured in the Dagster+ UI, or using the dagster-cloud CLI tool.

Prerequisites
  • Organization, Admin, or Editor permissions on Dagster+

Configuring a notification service​

To start, you'll need to configure a service to send alerts. Dagster+ current supports sending alerts through email, Microsoft Teams, PagerDuty, and Slack.

No additional configuration is required to send emails from Dagster+.

All alert emails will be sent by "no-reply@dagster.cloud" or "no-reply@<subdomain>.dagster.cloud". Alerts can be configured to be sent to any number of emails.

Alerting when a run fails​

You can set up alerts to notify you when a run fails.

By default, these alerts will target all runs in the deployment, but they can be scoped to runs with a specific tag.

  1. In the Dagster UI, click Deployment.

  2. Click the Alerts tab.

  3. Click Add alert policy.

  4. Select Run alert from the dropdown.

  5. Select Job failure.

If desired, add tags in the format {key}:{value} to filter the runs that will be considered.

Alerting when a run is taking too long to complete​

You can set up alerts to notify you whenever a run takes more than some threshold amount of time.

By default, these alerts will target all runs in the deployment, but they can be scoped to runs with a specific tag.

  1. In the Dagster UI, click Deployment.

  2. Click the Alerts tab.

  3. Click Add alert policy.

  4. Select Run alert from the dropdown.

  5. Select Job running over and how many hours to alert after.

If desired, add tags in the format {key}:{value} to filter the runs that will be considered.

Alerting when an asset fails to materialize​

You can set up alerts to notify you when an asset materialization attempt fails.

By default, these alerts will target all assets in the deployment, but they can be scoped to a specific asset or group of assets.

  1. In the Dagster UI, click Deployment.

  2. Click the Alerts tab.

  3. Click Add alert policy.

  4. Select Asset alert from the dropdown.

  5. Select Failure under the Materializations heading.

If desired, select a target from the dropdown menu to scope this alert to a specific asset or group.

Alerting when an asset check fails​

You can set up alerts to notify you when an asset check on an asset fails.

By default, these alerts will target all assets in the deployment, but they can be scoped to checks on a specific asset or group of assets.

  1. In the Dagster UI, click Deployment.

  2. Click the Alerts tab.

  3. Click Add alert policy.

  4. Select Asset alert from the dropdown.

  5. Select Failed (ERROR) under the Asset Checks heading.

If desired, select a target from the dropdown menu to scope this alert to a specific asset or group.

Alerting when a schedule or sensor tick fails​

You can set up alerts to fire when any schedule or sensor tick across your entire deployment fails.

Alerts are sent only when a schedule/sensor transitions from success to failure, so only the initial failure will trigger the alert.

  1. In the Dagster UI, click Deployment.
  2. Click the Alerts tab.
  3. Click Add alert policy.
  4. Select Schedule/Sensor alert from the dropdown.

Alerting when a code location fails to load​

You can set up alerts to fire when any code location fails to load due to an error.

  1. In the Dagster UI, click Deployment.
  2. Click the Alerts tab.
  3. Click Add alert policy.
  4. Select Code location error alert from the dropdown.

Alerting when a Hybrid agent becomes unavailable​

note

This is only available for Hybrid deployments.

You can set up alerts to fire if your Hybrid agent hasn't sent a heartbeat in the last 5 minutes.

  1. In the Dagster UI, click Deployment.
  2. Click the Alerts tab.
  3. Click Add alert policy.
  4. Select Code location error alert from the dropdown.