Route tagged Airflow DAG-run events to alerting and metric backends.
Tag a DAG with P1 through P5 and configure the destinations that should receive its state changes. Backends apply independent thresholds. The plugin observes DAG-run running, success, and failure events through Airflow listeners.
- Tutorial: alert on one failed DAG sends a tagged failure to a Slack test channel.
- How-to guides cover priorities, thresholds, environment variables, airflow-config, and delivery troubleshooting.
- API reference lists configuration models, backend options, routing, listener hooks, and tracker behavior.
- Why priority alerts follow DAG-run state explains task callbacks, recovery workflows, and process-local context.
Backend guides cover Slack, Discord, PagerDuty, Opsgenie, Symphony, Datadog, New Relic, Logfire, and AWS CloudWatch. The email guide uses Airflow's configured email backend.
Published documentation: airflow-laminar.github.io/airflow-priority.
airflow-supervisor, airflow-nomad, and airflow-cron produce task logs and failure diagnostics. Priority routing observes their DAG outcomes; task callbacks handle task-specific notification needs.
Apache 2.0. See LICENSE.