Log inspection and troubleshooting in Apache Airflow - Time & Space Complexity

Time Complexity: Log inspection and troubleshooting

O(n * m)

Understanding Time Complexity

When we inspect logs in Airflow, we want to know how the time to find issues grows as logs get bigger.

We ask: How does the effort to search logs change when there are more log entries?

Scenario Under Consideration

Analyze the time complexity of the following Airflow log inspection code.

from airflow.models import TaskInstance

def inspect_logs(task_instances):
    errors = []
    for ti in task_instances:
        log = ti.log.read()
        if 'ERROR' in log:
            errors.append(ti.task_id)
    return errors
    

This code checks each task instance's log for the word "ERROR" and collects task IDs with errors.

Identify Repeating Operations

Look at what repeats in the code.

• Primary operation: Looping over all task instances and reading their logs.
• How many times: Once for each task instance in the input list.

How Execution Grows With Input

As the number of task instances grows, the time to check logs grows too.

Input Size (n)	Approx. Operations
10	10 log reads and checks
100	100 log reads and checks
1000	1000 log reads and checks

Pattern observation: The work grows directly with the number of task instances.

Final Time Complexity

Time Complexity: O(n * m)

This means the time to inspect logs grows linearly with the number of task instances and the size of each log.

Common Mistake

[X] Wrong: "Checking logs for errors is instant no matter how many tasks there are."

[OK] Correct: Each task's log must be read and checked, so more tasks mean more work and more time.

Interview Connect

Understanding how log inspection time grows helps you design better monitoring and troubleshooting tools in real projects.

Self-Check

"What if we cached logs after the first read? How would that change the time complexity?"

Practice

1. What is the main purpose of inspecting logs in Airflow tasks?

easy

A. To schedule new DAG runs

B. To change the task's code automatically

C. To understand what happened during task execution step-by-step

D. To delete old DAGs from Airflow

Solution

1. Step 1: Understand what logs represent in Airflow

   Logs record the detailed events and outputs of each task run, showing what happened inside the task.

2. Step 2: Identify the purpose of inspecting logs

   Inspecting logs helps to see the step-by-step execution and find errors or confirm success.

3. Final Answer:

   To understand what happened during task execution step-by-step -> Option C

4. Quick Check:

   Logs show task execution details = A [OK]

Hint: Logs tell the story of task steps and errors [OK]

Common Mistakes:

• Thinking logs change task code
• Confusing logs with scheduling
• Believing logs delete DAGs

2. Which command correctly shows logs for a task named process_data in DAG daily_report for date 2024-06-01?

easy

A. airflow tasks logs daily_report process_data 2024-06-01

B. airflow logs show daily_report process_data 2024-06-01

C. airflow show logs daily_report process_data 2024-06-01

D. airflow task logs daily_report process_data 2024-06-01

Solution

1. Step 1: Recall the correct airflow CLI syntax for logs

   The correct command is airflow tasks logs <dag_id> <task_id> <execution_date>.

2. Step 2: Match the command with given task and date

   airflow tasks logs daily_report process_data 2024-06-01 matches the syntax exactly with correct order and spelling.

3. Final Answer:

   airflow tasks logs daily_report process_data 2024-06-01 -> Option A

4. Quick Check:

   Correct airflow logs command = A [OK]

Hint: Use 'airflow tasks logs DAG task date' exactly [OK]

Common Mistakes:

• Swapping 'tasks' and 'logs' words
• Using 'show' or 'task' incorrectly
• Wrong command order

3. You run airflow tasks logs sales_report generate_summary 2024-06-02 and see an error about missing file. What does this log output indicate?

medium

A. The task succeeded without issues

B. The DAG did not run on that date

C. The Airflow scheduler is down

D. The task failed because it could not find a required file

Solution

1. Step 1: Analyze the log error message about missing file

   An error about a missing file means the task tried to access a file that does not exist or is not reachable.

2. Step 2: Understand the implication for task status

   This error causes the task to fail because it cannot complete its work without the file.

3. Final Answer:

   The task failed because it could not find a required file -> Option D

4. Quick Check:

   Missing file error means task failure = C [OK]

Hint: Missing file error means task failure [OK]

Common Mistakes:

• Assuming task succeeded despite error
• Confusing DAG run status with task logs
• Thinking scheduler status is shown in task logs

4. You try to view logs with airflow tasks logs my_dag my_task 2024-06-05 but get a 'No logs found' message. What is the most likely cause?

medium

A. The DAG is paused

B. The task has not run yet for that date

C. Airflow is not installed

D. The command syntax is incorrect

Solution

1. Step 1: Understand what 'No logs found' means in Airflow

   This message usually means no logs exist because the task has not executed for the given date.

2. Step 2: Check other options for plausibility

   The command syntax is correct, Airflow installed is unrelated, and paused DAGs still keep logs from past runs.

3. Final Answer:

   The task has not run yet for that date -> Option B

4. Quick Check:

   No logs means no task run yet = D [OK]

Hint: No logs means task not run yet for that date [OK]

Common Mistakes:

• Assuming command syntax error
• Thinking Airflow is missing
• Confusing paused DAG with no logs

5. You want to troubleshoot why your Airflow task data_cleanup in DAG weekly_maintenance fails intermittently. Which approach best helps you find the root cause using logs?

hard

A. Check logs for multiple recent runs to find patterns of failure

B. Delete all logs to force fresh logging

C. Restart Airflow scheduler without checking logs

D. Change the DAG schedule to run more often

Solution

1. Step 1: Understand the goal of troubleshooting intermittent failures

   Intermittent failures require comparing multiple runs to see when and why failures happen.

2. Step 2: Identify the best log inspection method

   Checking logs from several recent runs helps spot patterns or recurring errors causing failure.

3. Final Answer:

   Check logs for multiple recent runs to find patterns of failure -> Option A

4. Quick Check:

   Compare multiple logs to find failure patterns = B [OK]

Hint: Compare logs from several runs to spot failure patterns [OK]

Common Mistakes:

• Deleting logs loses important info
• Restarting scheduler ignores root cause
• Changing schedule doesn't fix errors