Using Dagster Cloud's built-in alerting system, you can stay in the loop on the events occurring in your deployment. Dagster Cloud alerts integrate with several popular services, allowing you to deliver notifications when and where they're most needed.
Alerts are created using alert policies. An alert policy defines the conditions that will trigger an alert and how the alert will be sent. For example, you can create a policy that sends an alert to a Slack channel when any asset in a specific asset group fails to materialize.
Alert policies are configured on a per-deployment basis. This means, for example, that asset alerts configured in a prod deployment are only applicable to assets in that deployment.
| Policy type | How it works |
|---|---|
| Asset alert | Triggers on:
|
| Run alert | Triggers on job run success or failure; may optionally include a set of configured tags. If an alert policy has no configured tags, all jobs will be eligible for that alert. Otherwise, only jobs that contain all the tags for a given alert policy are eligible for that alert. |
| Schedule/Sensor alert | Triggers when a schedule or sensor tick failure occurs for any schedule or sensor in the deployment. Note: Alerts are sent only when the schedule/sensor changes from success to failure, so subsequent failures won't trigger new alerts. |
| Code location error alert | Triggers when a code location fails to load due to an error. |
| Agent downtime alert | Triggers when a Hybrid agent hasn't heartbeated within the last five minutes. Available for Hybrid deployments only. |
Dagster Cloud can send notifications via:
Managing alert policies can be accomplished by using: