Contents Menu Expand Light mode Dark mode Auto light/dark, in light mode Auto light/dark, in dark mode Skip to content
airflow-priority v1.6.2
airflow-priority v1.6.2
  • Tutorial: alert on one failed DAG
  • How-to guides
  • Why priority alerts follow DAG-run state
  • API reference
    • airflow_priority.PriorityConfiguration
    • airflow_priority.AwsConfiguration
    • airflow_priority.DataDogConfiguration
    • airflow_priority.DiscordConfiguration
    • airflow_priority.LogfireConfiguration
    • airflow_priority.NewRelicConfiguration
    • airflow_priority.OpsGenieConfiguration
    • airflow_priority.PagerDutyConfiguration
    • airflow_priority.SlackConfiguration
    • airflow_priority.SymphonyConfiguration
    • airflow_priority.common
    • airflow_priority.plugin
    • airflow_priority.tracker.Tracker
  • Introduction
  • How to publish DAG status metrics to Datadog
  • How to send DAG failures to Discord
  • How to publish DAG status metrics to New Relic
  • How to alert an existing Opsgenie integration
  • How to publish DAG status metrics to Logfire
  • How to send DAG failures to Slack
  • How to create PagerDuty incidents for failed DAGs
  • How to send DAG failures to Symphony
  • How to publish DAG status metrics to CloudWatch
Back to top
View this page

IntroductionΒΆ

Start with the failure-alert tutorial, or follow the how-to guides to configure an existing deployment.

The reference defines backend options and routing. The explanation covers DAG-run state, task callbacks, and the limits of process-local alert context.

Next
How to publish DAG status metrics to Datadog
Previous
airflow_priority.tracker.Tracker
Copyright © the airflow-priority authors
Made with Sphinx and @pradyunsg's Furo