Alert policy types
| Policy type | Triggers on | Notes | Availability |
|---|---|---|---|
| Asset | Asset materializations - Failure or success. If you use a RetryPolicy, an alert will only be sent after all retries complete. Asset checks - Error, warn, passed, or failure to execute. By default, failed asset checks have a severity of WARN. | Asset alerts can be scoped to asset groups or specific asset keys. Asset check alerts are sent for any checks on those assets. On Dagster+ Pro, asset alerts also allow you to send alerts to asset owners. External assets do not trigger asset alerts. | Serverless and Hybrid deployments |
| Run | Triggers on job run success, failure, or time limit exceeded; 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. Each newly created organization starts with a long-running run alert policy, which sends an email to the email address used to create the organization when a job run exceeds 24 hours. | Serverless and Hybrid deployments |
| Code location | Triggers when a code location fails to load due to an error. | Serverless and Hybrid deployments | |
| Automation | Triggers when a tick failure occurs for schedules or sensors in the deployment. | Alerts are sent only when the schedule/sensor changes from success to failure, so subsequent failures won't trigger new alerts. You can also configure alerts to only fire after multiple consecutive failures. | Serverless and Hybrid deployments |
| Agent downtime | Triggers when a Hybrid agent hasn't heartbeated within the last five minutes. | Hybrid deployments only. | |
| Insights metric (Experimental) | Triggers when a Dagster+ Insights metric exceeds or falls below a specified threshold over a specified time window. This can be used to alert on:
| Alerts can be scoped to the sum of any metric across an entire deployment, or for a specific job, asset group, or asset key. Alerts are sent only when the threshold is first crossed, and will not be sent again until the value returns to expected levels. Insights data may become available up to 24 hours after run completion. | Serverless and Hybrid deployments |
| Credit budget (Experimental) | Triggers when your organization has reached the monthly credit limit. | Each newly created organization starts with an alert policy of this type, directed at the email address used to create the organization. | Serverless deployments only |