Alert policy types

When you create an alert policy, you must first select one of the policy types described below.

Policy type	Triggers on	Availability	Notes
Asset alert	Asset materializations - Failure or success. If using 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.	Serverless and Hybrid deployments	Asset alerts can be scoped to asset groups or specific asset keys. Asset check alerts are sent for any checks on those assets. If using Dagster+ Pro, asset alerts also allow you to send alerts to asset owners. External assets do not trigger asset alerts.
Run alert	Triggers on job run success, failure, or time limit exceeded; may optionally include a set of configured tags.	Serverless and Hybrid deployments	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.
Schedule/sensor alert	Triggers when a schedule or sensor tick failure occurs for any schedule or sensor in the deployment.	Serverless and Hybrid deployments	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.	Serverless and Hybrid deployments
Agent downtime alert	Triggers when a Hybrid agent hasn't heartbeated within the last five minutes.	Hybrid deployments only.
Insights metric alert (Experimental)	Sends a notification when a Dagster+ Insights metric exceeds or falls below a specified threshold over a specified time window. This can be used to alert on: Dagster credit usage across a deployment or for a specific job Performance regressions on asset or job runtime Spend on external tools such as Snowflake or BigQuery credits	Serverless and Hybrid deployments	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.
Credit budget alert (Experimental)	Sends a notification when your organization has reached the monthly credit limit.	Serverless deployments only	Each newly created organization starts with an alert policy of this type, directed at the email address used to create the organization.