SLA misses and notifications in Apache Airflow - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to set an SLA for a task in Airflow.

Apache Airflow

task = PythonOperator(task_id='my_task', python_callable=my_func, sla=[1])

Drag options to blanks, or click blank then click option'

Adatetime.now()

B30

C'30 minutes'

Dtimedelta(minutes=30)

Attempts:

3 left

💡 Hint

Common Mistakes

Using a string instead of timedelta

Using an integer directly

Using datetime.now() instead of timedelta

The sla parameter expects a timedelta object to define the SLA duration.

2fill in blank

medium

Complete the code to enable SLA miss notifications via email in Airflow's DAG.

Apache Airflow

default_args = {'email': ['[e-mail]'], 'email_on_[1]': True}

Drag options to blanks, or click blank then click option'

Asla_miss

Bsuccess

Cretry

Dfailure

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'email_on_failure' instead

Using 'email_on_retry' instead

Using 'email_on_success' instead

To receive notifications on SLA misses, set email_on_sla_miss to True.

3fill in blank

hard

Fix the error in the SLA miss callback function definition.

Apache Airflow

def sla_miss_callback([1]):
    print(f"SLA missed for task: [1]['task_instance'].task_id")

Drag options to blanks, or click blank then click option'

Adag_run

Btask_instance

Ccontext

Dkwargs

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'task_instance' directly as parameter

Using 'dag_run' instead of context

Using 'kwargs' without unpacking

The SLA miss callback receives a context dictionary with task and DAG info.

4fill in blank

hard

Fill both blanks to correctly access the task instance and send an email in the SLA miss callback.

Apache Airflow

def sla_miss_callback([1]):
    task_instance = [2]['task_instance']
    send_email('[e-mail]', f"SLA missed for {task_instance.task_id}")

Drag options to blanks, or click blank then click option'

Acontext

Bkwargs

Dparams

Attempts:

3 left

💡 Hint

Common Mistakes

Using different names for parameter and variable

Not accessing task_instance from context

The callback receives context and accesses task_instance from it.

5fill in blank

hard

Fill all three blanks to define a DAG with SLA miss callback and email notification.

Apache Airflow

default_args = {
    'owner': 'airflow',
    'start_date': datetime(2024, 1, 1),
    'email': ['[e-mail]'],
    'email_on_[1]': True,
    'sla_miss_callback': [2]
}

dag = DAG('sla_example', default_args=default_args, schedule_interval='@daily')

task = PythonOperator(task_id='task1', python_callable=my_func, sla=[3], dag=dag)

Drag options to blanks, or click blank then click option'

Asla_miss

Bsla_miss_callback

Ctimedelta(minutes=45)

Demail_on_failure

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong email notification key

Not assigning the callback function

Using wrong SLA value type

Set email_on_sla_miss to True, assign the callback function, and define SLA as timedelta.

Practice

1. What does setting an sla parameter on an Airflow task do?

easy

A. It defines a time limit; if the task runs longer, it triggers an SLA miss.

B. It sets the maximum retries for the task.

C. It schedules the task to run at a specific time.

D. It disables the task from running automatically.

Solution

1. Step 1: Understand the purpose of sla in Airflow tasks

   The sla parameter sets a time limit for task execution.

2. Step 2: Identify what happens when the limit is exceeded

   If the task runs longer than the sla time, Airflow marks it as an SLA miss.

3. Final Answer:

   It defines a time limit; if the task runs longer, it triggers an SLA miss. -> Option A

4. Quick Check:

   sla sets time limit = C [OK]

Hint: Remember SLA means max allowed time for task [OK]

Common Mistakes:

• Confusing SLA with retry count
• Thinking SLA schedules task start time
• Assuming SLA disables tasks

2. Which of the following is the correct way to define an SLA of 30 minutes on a task in Airflow?

easy

A. sla='30 minutes'

B. sla=30

C. sla=timedelta(minutes=30)

D. sla='00:30:00'

Solution

1. Step 1: Recall the correct data type for sla

   The sla parameter expects a datetime.timedelta object.

2. Step 2: Identify the correct syntax for 30 minutes timedelta

   timedelta(minutes=30) correctly creates a 30-minute duration.

3. Final Answer:

   sla=timedelta(minutes=30) -> Option C

4. Quick Check:

   sla uses timedelta object = B [OK]

Hint: Use timedelta for time durations in Airflow [OK]

Common Mistakes:

• Using string instead of timedelta
• Passing integer without timedelta
• Using incorrect string format

3. Given this DAG snippet, what will happen if task1 runs longer than 10 minutes?

from datetime import timedelta
from airflow import DAG
from airflow.operators.dummy import DummyOperator
from airflow.utils.dates import days_ago

def sla_miss_callback(dag, task_list, blocking_task_list, slas, session=None):
    print('SLA missed!')

dag = DAG('sla_example', start_date=days_ago(1))

task1 = DummyOperator(
    task_id='task1',
    dag=dag,
    sla=timedelta(minutes=10)
)

dag.sla_miss_callback = sla_miss_callback

medium

A. The sla_miss_callback function will print 'SLA missed!' when the SLA is missed.

B. Nothing happens because DummyOperator ignores SLA.

C. The task will automatically retry until it finishes within 10 minutes.

D. Airflow will fail the DAG immediately.

Solution

1. Step 1: Understand SLA miss callback usage

   The DAG-level sla_miss_callback is called when any task misses its SLA.

2. Step 2: Identify what the callback does

   The callback prints 'SLA missed!' when triggered by a task exceeding its SLA.

3. Final Answer:

   The sla_miss_callback function will print 'SLA missed!' when the SLA is missed. -> Option A

4. Quick Check:

   SLA miss triggers callback print = A [OK]

Hint: SLA miss triggers callback, not retries or failure [OK]

Common Mistakes:

• Thinking SLA causes retries automatically
• Assuming DummyOperator ignores SLA
• Believing DAG fails immediately on SLA miss

4. You wrote this code to notify on SLA misses but no notification happens:

def notify_sla_miss(dag, task_list, blocking_task_list, slas, session=None):
    send_email('[e-mail]', 'SLA Missed')

dag = DAG('sla_notify', start_date=days_ago(1), sla_miss_callback=notify_sla_miss)

task = DummyOperator(task_id='task', dag=dag, sla=timedelta(minutes=5))

What is the likely reason notifications are not sent?

medium

A. DummyOperator does not support SLA misses.

B. SLA miss callback must be set on the task, not the DAG.

C. The SLA time must be set in seconds, not minutes.

D. The send_email function is not defined or imported.

Solution

1. Step 1: Check the callback function implementation

   The callback calls send_email but no import or definition is shown.

2. Step 2: Understand Airflow's email sending

   Airflow requires proper email function or operator; undefined send_email causes failure silently.

3. Final Answer:

   The send_email function is not defined or imported. -> Option D

4. Quick Check:

   Undefined email function blocks notification = D [OK]

Hint: Ensure email functions are imported or use Airflow email operators [OK]

Common Mistakes:

• Setting callback on DAG instead of task (both valid but DAG preferred)
• Wrong SLA time units
• Assuming DummyOperator ignores SLA

5. You want to send a custom Slack message when any task misses its SLA in your DAG. Which approach correctly implements this?

hard

A. Set sla on tasks and add a SlackOperator as a downstream task to notify SLA misses.

B. Define a sla_miss_callback function that uses Slack API and assign it to the DAG's sla_miss_callback parameter.

C. Use on_failure_callback on tasks to send Slack messages when SLA is missed.

D. Configure Airflow to send Slack notifications by setting sla to the Slack channel name.

Solution

1. Step 1: Understand how SLA miss notifications work

   SLA misses trigger the sla_miss_callback function assigned to the DAG or task.

2. Step 2: Identify correct way to send Slack message on SLA miss

   Implement a callback function that calls Slack API and assign it to DAG's sla_miss_callback.

3. Final Answer:

   Define a sla_miss_callback function that uses Slack API and assign it to the DAG's sla_miss_callback parameter. -> Option B

4. Quick Check:

   SLA miss callback with Slack API = A [OK]

Hint: Use sla_miss_callback with Slack API for notifications [OK]

Common Mistakes:

• Using on_failure_callback instead of sla_miss_callback
• Trying to notify via downstream tasks
• Misconfiguring sla parameter as Slack channel