Integration with PagerDuty and Slack in Apache Airflow - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Output of Airflow task notifying PagerDuty

Given this Airflow PythonOperator task code snippet that triggers a PagerDuty incident notification, what will be the output in the Airflow logs if the PagerDuty API key is invalid?

Apache Airflow

def notify_pagerduty():
    import requests
    url = 'https://events.pagerduty.com/v2/enqueue'
    payload = {
        "routing_key": "INVALID_API_KEY",
        "event_action": "trigger",
        "payload": {
            "summary": "Test incident",
            "source": "airflow",
            "severity": "error"
        }
    }
    response = requests.post(url, json=payload)
    print(response.status_code)
    print(response.json())

A

400
{'status': 'error', 'message': 'Invalid routing key', 'errors': ['Routing key is invalid']}

B

200
{'status': 'success', 'message': 'Event processed', 'dedup_key': 'abc123'}

C

500
{'status': 'error', 'message': 'Internal server error'}

D

401
{'status': 'error', 'message': 'Unauthorized', 'errors': ['Invalid API key']}

💡 Hint

Think about what HTTP status code PagerDuty returns for invalid keys.

PagerDuty returns a 400 Bad Request status with a message indicating the routing key is invalid when the API key is wrong.

❓ Configuration

intermediate

Correct Slack webhook URL format in Airflow Variable

Which of the following is the correct format to store a Slack Incoming Webhook URL in an Airflow Variable for use in a Slack notification task?

A slack://hooks.slack.com/services/T00000000/B00000000/XXXXXXXXXXXXXXXXXXXXXXXX

B hooks.slack.com/services/T00000000/B00000000/XXXXXXXXXXXXXXXXXXXXXXXX

C http://hooks.slack.com/services/T00000000/B00000000/XXXXXXXXXXXXXXXXXXXXXXXX

D https://hooks.slack.com/services/T00000000/B00000000/XXXXXXXXXXXXXXXXXXXXXXXX

💡 Hint

Slack webhooks use HTTPS URLs starting with https://

The Slack Incoming Webhook URL must start with https:// to be valid and secure.

🔀 Workflow

advanced

Order of steps to integrate Airflow with PagerDuty and Slack

Arrange the steps in the correct order to integrate Airflow with PagerDuty and Slack for alert notifications.

A 1,2,3,4

B 2,1,3,4

C 3,1,2,4

D 1,3,2,4

💡 Hint

Think about what credentials you need before storing and using them.

You must first create the PagerDuty service and Slack webhook, then store their keys in Airflow, and finally create tasks that use those keys.

❓ Troubleshoot

advanced

Identifying cause of Slack notification failure in Airflow

An Airflow task that sends Slack notifications fails with this error: "requests.exceptions.ConnectionError: HTTPSConnectionPool(host='hooks.slack.com', port=443): Max retries exceeded". What is the most likely cause?

A The Slack webhook URL is incorrect or malformed

B The Slack API token has expired

C The Airflow worker has no internet access or network issues

D The Airflow DAG code has a syntax error

💡 Hint

Connection errors usually relate to network problems.

Max retries exceeded on HTTPS connection usually means network connectivity issues, such as no internet access from Airflow worker.

✅ Best Practice

expert

Best practice for secure storage of PagerDuty and Slack credentials in Airflow

Which is the best practice for securely managing PagerDuty routing keys and Slack webhook URLs in Airflow for production use?

A Store keys in environment variables on Airflow workers only

B Use Airflow's built-in Secret Backend to store and retrieve keys securely

C Store keys as plain text in Airflow Variables with no encryption

D Hardcode keys directly in DAG Python code for easy access

💡 Hint

Think about how to keep secrets safe and avoid exposure in code or UI.

Using Airflow's Secret Backend allows secure encrypted storage and controlled access to sensitive keys.