Logging and log analysis in Drone Programming - Step-by-Step Execution

Concept Flow - Logging and log analysis

Start Drone Operation

↓

Generate Logs

↓

Store Logs

↓

Analyze Logs

↓

Detect Issues or Confirm Success

↓

Take Action or Continue Operation

This flow shows how a drone operation creates logs, stores them, analyzes them, and then uses the results to decide what to do next.

Execution Sample

Drone Programming

battery = 80
log("Drone started")
log("Altitude: 100m")
log("Battery: 80%")
if battery < 20:
  log("Warning: Low battery")
log("Drone landing")

This code logs drone status messages and warns if the battery is low.

Execution Table

Step	Action	Log Message	Condition Checked	Result
1	Log start message	Drone started	N/A	Message stored
2	Log altitude	Altitude: 100m	N/A	Message stored
3	Log battery level	Battery: 80%	N/A	Message stored
4	Check battery < 20	N/A	80 < 20?	False, no warning logged
5	Log landing message	Drone landing	N/A	Message stored

💡 All steps completed, no low battery warning triggered

Variable Tracker

Variable	Start	After Step 3	After Step 4	Final
battery	N/A	80	80	80

Key Moments - 2 Insights

Why is there no 'Warning: Low battery' log even though we check battery?

Because at step 4 in the execution_table, the battery value is 80 which is not less than 20, so the warning log is skipped.

What happens to logs after they are generated?

Logs are stored immediately after each log() action as shown in the 'Result' column of the execution_table.

Visual Quiz - 3 Questions

Look at the execution_table, what is logged at step 2?

A Altitude: 100m

B Battery: 80%

C Drone started

D Drone landing

💡 Hint

Check the 'Log Message' column for step 2 in the execution_table

At which step does the battery condition get checked?

A Step 5

B Step 3

C Step 4

D Step 2

💡 Hint

Look at the 'Condition Checked' column in the execution_table

If battery was 10 instead of 80, what would happen at step 4?

A No warning logged

B Warning: Low battery logged

C Drone landing logged

D Battery log skipped

💡 Hint

Refer to the 'Result' column for step 4 and imagine battery < 20 is true

Concept Snapshot

Logging records events during drone operation.
Logs are stored immediately for later review.
Conditions can trigger special logs (e.g., warnings).
Analyzing logs helps detect problems or confirm success.
Logs guide decisions during and after flight.

Full Transcript

This visual execution shows how a drone program logs messages step-by-step. It starts by logging the drone start, altitude, and battery level. Then it checks if the battery is low. Since the battery is 80, no warning is logged. Finally, it logs the drone landing. Variables like battery are tracked through the steps. Key moments clarify why warnings appear or not. Quiz questions test understanding of log messages and conditions.

Practice

1. What is the main purpose of logging in drone programming?

easy

A. To reduce the drone's battery usage

B. To speed up the drone's flight

C. To change the drone's hardware settings

D. To record what the drone program does step by step

Solution

1. Step 1: Understand logging basics

   Logging means saving messages about what the program is doing.

2. Step 2: Identify the main goal of logging

   It helps track the program's actions step by step for review or debugging.

3. Final Answer:

   To record what the drone program does step by step -> Option D

4. Quick Check:

   Logging = record steps [OK]

Hint: Logging means writing down program actions stepwise [OK]

Common Mistakes:

• Confusing logging with hardware control
• Thinking logging speeds up the drone
• Assuming logging saves battery

2. Which of the following is the correct syntax to log an info message in a drone program using Python's logging module?

easy

A. log.info("Drone started flying")

B. logging.info("Drone started flying")

C. logging.loginfo("Drone started flying")

D. logging.info: "Drone started flying"

Solution

1. Step 1: Recall Python logging syntax

   The correct method to log info level messages is logging.info(message).

2. Step 2: Check each option

   logging.info("Drone started flying") matches the correct syntax exactly; others have wrong method names or punctuation.

3. Final Answer:

   logging.info("Drone started flying") -> Option B

4. Quick Check:

   logging.info() is correct method [OK]

Hint: Use logging.info("message") to log info level [OK]

Common Mistakes:

• Using wrong method names like log.info or logging.loginfo
• Using colon instead of parentheses
• Missing parentheses around the message

3. Given this Python code snippet for logging in a drone program:

import logging
logging.basicConfig(level=logging.WARNING)
logging.debug("Debug message")
logging.warning("Warning message")
logging.error("Error message")

What will be printed to the console?

medium

A. Warning message\nError message

B. Debug message\nWarning message\nError message

C. Error message only

D. No output

Solution

1. Step 1: Understand logging level setting

   basicConfig sets level to WARNING, so messages with level WARNING and above show.

2. Step 2: Check each log call

   debug is below WARNING, so not shown; warning and error are shown.

3. Final Answer:

   Warning message\nError message -> Option A

4. Quick Check:

   Level WARNING shows warning and error [OK]

Hint: Logs show messages at or above set level [OK]

Common Mistakes:

• Expecting debug messages to appear
• Thinking only error shows at WARNING level
• Confusing logging levels order

4. You see this error in your drone program logs:
AttributeError: 'Logger' object has no attribute 'loginfo'
What is the most likely cause?

medium

A. Setting logging level too high

B. Not importing the logging module

C. Using a wrong logging method name like loginfo instead of info

D. Logging message is empty

Solution

1. Step 1: Analyze the error message

   AttributeError means the Logger object does not have the called method.

2. Step 2: Identify the method name mistake

   loginfo is not a valid method; correct is info.

3. Final Answer:

   Using a wrong logging method name like loginfo instead of info -> Option C

4. Quick Check:

   Method name must be correct [OK]

Hint: Check method names carefully for typos [OK]

Common Mistakes:

• Assuming import error causes AttributeError
• Thinking logging level causes method errors
• Ignoring method name spelling

5. You want to analyze drone logs to find all error messages that happened between 2pm and 3pm. Which approach is best?

hard

A. Filter logs by timestamp and error level using a log analysis tool

B. Manually read the entire log file line by line

C. Change the drone code to print only errors during that hour

D. Delete all logs except those from 2pm to 3pm

Solution

1. Step 1: Understand log analysis goal

   You want to find error messages in a specific time range efficiently.

2. Step 2: Choose best method

   Using a log analysis tool to filter by timestamp and error level is efficient and accurate.

3. Final Answer:

   Filter logs by timestamp and error level using a log analysis tool -> Option A

4. Quick Check:

   Use tools to filter logs by time and level [OK]

Hint: Use tools to filter logs by time and error level [OK]

Common Mistakes:

• Trying to read logs manually which is slow
• Changing code instead of analyzing existing logs
• Deleting logs risks losing data