Integration with PagerDuty and Slack in Apache Airflow - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is PagerDuty used for in Airflow integrations?

PagerDuty is used to send alerts and incident notifications when Airflow tasks fail or encounter issues, helping teams respond quickly.

beginner

How does Slack integration help in Airflow monitoring?

Slack integration allows Airflow to send messages directly to Slack channels or users about task statuses, making it easy to track workflows in real time.

intermediate

Which Airflow operator or hook is commonly used to send messages to Slack?

The SlackAPIPostOperator or SlackWebhookOperator is commonly used to send messages to Slack from Airflow DAGs.

intermediate

What is required to configure PagerDuty integration in Airflow?

You need a PagerDuty service integration key and configure Airflow's PagerDuty webhook or use a custom operator to send alerts.

beginner

Why is it important to integrate Airflow with communication tools like Slack and PagerDuty?

Integration ensures that teams get immediate notifications about workflow issues, reducing downtime and improving response times.

Which Airflow operator is used to send messages to Slack?

A PagerDutyOperator

B SlackAPIPostOperator

C EmailOperator

D HttpSensor

SlackAPIPostOperator is designed to send messages to Slack channels or users.

What do you need from PagerDuty to send alerts from Airflow?

A Email address

B Slack webhook URL

C PagerDuty service integration key

D API token for GitHub

PagerDuty service integration key is required to authenticate and send alerts.

Why integrate Airflow with Slack?

A To get real-time workflow notifications

B To run Airflow DAGs faster

C To store logs

D To schedule tasks

Slack integration helps teams receive real-time notifications about workflow status.

What type of messages does PagerDuty handle from Airflow?

A Incident alerts and notifications

B Daily reports

C Task scheduling commands

D Slack messages

PagerDuty handles incident alerts to notify teams about failures or issues.

Which of these is NOT a benefit of integrating Airflow with PagerDuty and Slack?

A Faster incident response

B Improved team communication

C Immediate alerting on failures

D Automatic task retries

Automatic task retries are handled by Airflow itself, not by PagerDuty or Slack.

Explain how you would set up Airflow to send failure alerts to PagerDuty and Slack.

Think about keys, webhooks, and operators.

Describe the benefits of integrating Airflow with PagerDuty and Slack for a team managing workflows.

Focus on team response and communication.

Practice

1. What is the main purpose of integrating Airflow with PagerDuty and Slack?

easy

A. To store Airflow logs in PagerDuty and Slack

B. To schedule Airflow DAGs automatically

C. To replace Airflow's scheduler with PagerDuty

D. To receive fast alerts and notifications about workflow issues

Solution

1. Step 1: Understand the role of PagerDuty and Slack in Airflow

   PagerDuty and Slack are used to send alerts and notifications when Airflow workflows have issues or important events.

2. Step 2: Identify the main benefit of integration

   The integration helps teams respond quickly by notifying them immediately about failures or important status updates.

3. Final Answer:

   To receive fast alerts and notifications about workflow issues -> Option D

4. Quick Check:

   Alerts and notifications = C [OK]

Hint: Think: Why notify teams fast? Alerts! [OK]

Common Mistakes:

• Confusing scheduling with alerting
• Thinking logs are stored in PagerDuty or Slack
• Assuming PagerDuty replaces Airflow scheduler

2. Which Airflow operator is used to send alerts to PagerDuty within a DAG?

easy

A. PagerDutyIncidentOperator

B. SlackAPIPostOperator

C. EmailOperator

D. HttpSensor

Solution

1. Step 1: Identify operators for PagerDuty and Slack

   SlackAPIPostOperator sends messages to Slack, PagerDutyIncidentOperator sends incidents to PagerDuty.

2. Step 2: Match operator to PagerDuty alerts

   PagerDutyIncidentOperator is designed specifically for PagerDuty integration.

3. Final Answer:

   PagerDutyIncidentOperator -> Option A

4. Quick Check:

   PagerDuty alerts = PagerDutyIncidentOperator A [OK]

Hint: PagerDuty operator name includes 'PagerDuty' [OK]

Common Mistakes:

• Choosing SlackAPIPostOperator for PagerDuty alerts
• Confusing EmailOperator with PagerDuty integration
• Selecting HttpSensor which is unrelated

3. Given this Airflow DAG snippet, what will be the output when the task notify_slack runs successfully?

notify_slack = SlackAPIPostOperator(
    task_id='notify_slack',
    token='xoxb-1234',
    channel='#alerts',
    text='DAG completed successfully!'
)

medium

A. No message is sent because the channel name is incorrect

B. An error occurs because the token is invalid

C. A message 'DAG completed successfully!' is posted to the #alerts Slack channel

D. The DAG fails to run because SlackAPIPostOperator is deprecated

Solution

1. Step 1: Understand SlackAPIPostOperator parameters

   The operator sends a message to the specified Slack channel using the provided token and text.

2. Step 2: Analyze the given snippet

   The token and channel are set, and the text is 'DAG completed successfully!'. If the token is valid, the message posts successfully.

3. Final Answer:

   A message 'DAG completed successfully!' is posted to the #alerts Slack channel -> Option C

4. Quick Check:

   Slack message sent = D [OK]

Hint: SlackAPIPostOperator posts text to channel if token valid [OK]

Common Mistakes:

• Assuming token is invalid without evidence
• Thinking SlackAPIPostOperator is deprecated
• Confusing channel name format

4. You wrote this task to send a PagerDuty alert but it fails with an authentication error:

pagerduty_alert = PagerDutyIncidentOperator(
    task_id='pagerduty_alert',
    routing_key='invalid_key',
    title='Airflow failure',
    severity='critical'
)

What is the most likely cause of the failure?

medium

A. The routing_key is incorrect or invalid

B. The severity value must be 'low' instead of 'critical'

C. PagerDutyIncidentOperator does not support the title parameter

D. The task_id must be 'pagerduty_incident' exactly

Solution

1. Step 1: Check the routing_key parameter

   The routing_key is a secret token that must be valid for PagerDuty API authentication.

2. Step 2: Understand authentication errors

   An invalid routing_key causes authentication failure, blocking alert creation.

3. Final Answer:

   The routing_key is incorrect or invalid -> Option A

4. Quick Check:

   Authentication error = invalid routing_key A [OK]

Hint: Authentication errors usually mean bad keys or tokens [OK]

Common Mistakes:

• Changing severity to fix authentication
• Removing title parameter incorrectly
• Changing task_id unnecessarily

5. You want to create an Airflow DAG that sends a Slack message only if a PagerDuty incident is triggered. Which approach correctly integrates both operators to achieve this?

hard

A. Use PagerDutyIncidentOperator first, then SlackAPIPostOperator with a trigger rule 'all_done' to send Slack message regardless of PagerDuty success

B. Use PagerDutyIncidentOperator first, then SlackAPIPostOperator with trigger rule 'all_success' to send Slack message only if PagerDuty alert succeeds

C. Use SlackAPIPostOperator first, then PagerDutyIncidentOperator with trigger rule 'one_failed' to send PagerDuty alert only if Slack fails

D. Use both operators in parallel without dependencies to send alerts simultaneously

Solution

1. Step 1: Define the desired workflow

   Slack message should be sent only if PagerDuty incident is successfully triggered.

2. Step 2: Set operator order and trigger rules

   Run PagerDutyIncidentOperator first. Set SlackAPIPostOperator to run after it with trigger_rule='all_success' to ensure Slack message only sends if PagerDuty alert succeeds.

3. Final Answer:

   Use PagerDutyIncidentOperator first, then SlackAPIPostOperator with trigger rule 'all_success' to send Slack message only if PagerDuty alert succeeds -> Option B

4. Quick Check:

   Slack after PagerDuty success = B [OK]

Hint: Slack depends on PagerDuty success with 'all_success' trigger [OK]

Common Mistakes:

• Sending Slack message regardless of PagerDuty result
• Reversing operator order
• Running both operators in parallel without dependency