Setting up alerts in Dagster Cloud#

In this guide, we'll walk you through configuring job and run alerts in Dagster Cloud.

Understanding alert policies#

Alert policies define which events will trigger an alert, the conditions under which an alert will be sent, and how the alert will be sent.

Currently, alerts can be triggered by job run failure/success, schedule/sensor tick failure, code location load error, and agent downtime.

• Job run based alert policies 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.
• Alert policies created for schedule/sensor tick failure will apply to all schedules/sensors. However, you will only receive alerts when the schedule/sensor changes from a state of succeeding to failing, so subsequent failures will not trigger new alerts.
• Code location error alert policies will trigger when a code location fails to load due to an error.
• Agent downtime alert policies will trigger when a Hybrid agent stops heart beating.

Alert policies are configured on a per-deployment basis. For example, alerts configured in a prod deployment are only applicable to jobs in that deployment.

Currently, Slack and email notifications are supported.

Managing alert policies in Dagster Cloud#

• Creating alert policies
• Editing alert policies
• Enabling and disabling alert policies
• Deleting alert policies

Creating alert policies#

1. Sign in to your Dagster Cloud account.

2. In the top navigation, click Deployment

3. Click the Alerts tab.

4. Click + Create alert policy.

5. From the Alert Policy type drop-down, select Run alert, Schedule/Sensor alert, Code location error alert, or Agent downtime alert.

6. In the Create alert policy window, fill in the following:

   • Alert policy name - Enter a name for the alert policy. For example, slack_urgent_failure
   • Description - Enter a description for the alert policy

   For run-based alerts, fill out these additional options:

   • Tags - Add tag(s) for the alert policy. Jobs with these tags will trigger the alert. For example: level:critical or team:sales

   • Events - Select whether the alert should trigger on job success, failure, or both

   • Notification service - Select the service for the alert policy:

     • Slack - If you haven't connected Slack, click Connect to add the Dagster Cloud Slack app to your workspace. After the installation completes, invite the @Dagster Cloud bot user to the desired channel.

       You can then configure the alert policy to message this channel. Note: Only messaging one channel per alert policy is currently supported:

       

     • Email - Email alerts can be sent to one or more recipients. For example:

       

7. When finished, click Save policy.

Editing alert policies#

To edit an existing alert policy, click the Edit button next to the policy:

Enabling and disabling alert policies#

To enable or disable an alert, use the toggle on the left side of the alert policy.

Deleting alert policies#

To delete an alert policy, click the Delete button next to the policy. When prompted, confirm the deletion.

Managing alert policies with the dagster-cloud CLI#

With the dagster-cloud CLI, you can:

• Set a full deployment's policies
• View a full deployment's policies
• Configure a Slack alert policy
• Configure an email alert policy

Setting a full deployment's policies#

A list of alert policies can be defined in a single YAML file. After declaring your policies, set them for the deployment using the following command:

dagster-cloud deployment alert-policies sync -a <ALERT_POLICIES_PATH>

Viewing a full deployment's policies#

List the policies currently configured on the deployment by running:

dagster-cloud deployment alert-policies list

Configuring a Slack alert policy#

In this example, we'll configure a Slack notification to trigger whenever a run of a job succeeds or fails. This job, named sales_job, has a team tag of sales:

@op
def sales_computation():
    ...


@job(tags={"team": "sales"})
def sales_job():
    sales_computation()

In the alert policies YAML file, we'll define a policy that listens for jobs with a team tag of sales to succeed or fail. When this occurs, a notification will be sent to the sales-notification channel in the hooli workspace:

alert_policies:
  - name: "slack-alert-policy"
    description: "An alert policy to send a Slack notification to sales on job failure or success."
    tags:
      - key: "team"
        value: "sales"
    event_types:
      - "JOB_SUCCESS"
      - "JOB_FAILURE"
    notification_service:
      slack:
        slack_workspace_name: "hooli"
        slack_channel_name: "sales-notifications"

Configuring an email alert policy#

In this example, we'll configure an email alert when a job fails. This job, named important_job, has a level tag of "critical":

def important_computation():
    ...


@job(tags={"level": "critical"})
def important_job():
    important_computation()

In the alert policies YAML file, we'll define a policy that listens for jobs with a level tag of critical to fail. When this occurs, an email notification will be sent to richard.hendricks@hooli.com and nelson.bighetti@hooli.com:

alert_policies:
  - name: "email-alert-policy"
    description: "An alert policy to email company executives during job failure."
    tags:
      - key: "level"
        value: "critical"
    event_types:
      - "JOB_FAILURE"
    notification_service:
      email:
        email_addresses:
          - "richard.hendricks@hooli.com"
          - "nelson.bighetti@hooli.com"

Compatible event types#

When creating an alert policy using the CLI, only certain event_types can be specified together. You can specify multiple job run-based event types together (JOB_SUCCESS, JOB_FAILURE), or a tick-based event type (TICK_FAILURE), but attempting to mix these will result in an error.