Logging in production in Flask - Step-by-Step Execution

Concept Flow - Logging in production

Start Flask App

↓

Configure Logger

↓

App Running

↓

Event Occurs

↓

Logger Records Event

↓

Log Stored in File or External System

↓

Monitor Logs for Issues

This flow shows how a Flask app starts, sets up logging, records events during runtime, and stores logs for monitoring.

Execution Sample

Flask

import logging
from flask import Flask
app = Flask(__name__)
logging.basicConfig(filename='app.log', level=logging.INFO)
@app.route('/')
def home():
    app.logger.info('Home page accessed')
    return 'Hello, world!'

This code sets up a Flask app with logging to a file and logs a message when the home page is accessed.

Execution Table

Step	Action	Logger State	Log Output	Result
1	Start Flask app	Logger configured, no logs yet	None	App ready to receive requests
2	Receive GET request at '/'	Logger ready	None	home() function called
3	home() logs info message	Logger has one INFO log	INFO:flask.app:Home page accessed	Log written to app.log
4	home() returns response	Logger unchanged	None	Client receives 'Hello, world!'
5	No more requests	Logger unchanged	None	App waits for next event

💡 No more requests, app continues running waiting for events

Variable Tracker

Variable	Start	After Step 3	Final
app.logger	Configured with INFO level	Contains 1 log entry	Contains 1 log entry

Key Moments - 2 Insights

Why don't we see log output immediately on the console?

Because logging is configured to write to a file ('app.log'), so logs are stored there instead of printing to the console. See execution_table step 3.

What happens if the log level is set to WARNING but we log an INFO message?

The INFO message will be ignored and not recorded because the logger only records messages at WARNING level or higher. This is why setting the correct log level is important.

Visual Quiz - 3 Questions

Look at the execution table at step 3. What does the logger do?

A It prints the message to the console

B It writes an INFO message to the log file

C It ignores the message because it's too low level

D It crashes the app

💡 Hint

Check the 'Log Output' column at step 3 in the execution_table

At which step does the Flask app respond to the client?

A Step 1

B Step 2

C Step 4

D Step 5

💡 Hint

Look at the 'Result' column for when the client receives a response

If we change logging level to WARNING, what happens to the INFO log in step 3?

A It is ignored and not logged

B It is still logged

C It causes an error

D It is logged twice

💡 Hint

Refer to key_moments about log levels and filtering

Concept Snapshot

Flask logging in production:
- Configure logging with logging.basicConfig(filename, level)
- Use app.logger.info/debug/warning to log events
- Logs go to file or external system, not console by default
- Set appropriate log level to filter messages
- Logs help monitor app behavior and troubleshoot

Full Transcript

This visual execution shows how a Flask app sets up logging to a file and records an info message when the home page is accessed. The app starts, configures the logger to write INFO level logs to 'app.log', then when a client requests the home page, the app logs 'Home page accessed' to the file. The client receives the response 'Hello, world!'. The logger state changes from empty to having one log entry. Key points include understanding that logs go to a file, not console, and that log levels control which messages are recorded. The quiz tests understanding of when logs are written, when responses are sent, and how log levels affect logging.

Practice

1. What is the main purpose of logging in a Flask application running in production?

easy

A. To speed up the app response time

B. To record app activity and errors for troubleshooting

C. To store user passwords securely

D. To create user interface themes

Solution

1. Step 1: Understand logging purpose

   Logging records events and errors to help developers understand app behavior.

2. Step 2: Identify production needs

   In production, logs help find and fix issues without stopping the app.

3. Final Answer:

   To record app activity and errors for troubleshooting -> Option B

4. Quick Check:

   Logging = record activity/errors [OK]

Hint: Logging tracks errors and events in production apps [OK]

Common Mistakes:

• Thinking logging speeds up the app
• Confusing logging with security features
• Assuming logging changes UI

2. Which of the following is the correct way to configure logging to write to a file named app.log with level WARNING in Flask?

easy

A. logging.basicConfig(filename='app.log', level=logging.WARNING)

B. logging.setup(filename='app.log', level='WARNING')

C. app.logger.config(filename='app.log', level=logging.WARNING)

D. logging.fileConfig('app.log', level=logging.WARNING)

Solution

1. Step 1: Recall logging setup syntax

   Use logging.basicConfig() with filename and level parameters.

2. Step 2: Check each option

   Only logging.basicConfig(filename='app.log', level=logging.WARNING) uses correct function and parameters.

3. Final Answer:

   logging.basicConfig(filename='app.log', level=logging.WARNING) -> Option A

4. Quick Check:

   basicConfig sets file and level [OK]

Hint: Use logging.basicConfig() to set file and level [OK]

Common Mistakes:

• Using wrong function names like setup or fileConfig
• Passing level as string instead of logging constant
• Trying to configure app.logger directly

3. Given this Flask route code, what will be logged when a user visits /hello?

import logging
from flask import Flask
app = Flask(__name__)

logging.basicConfig(filename='app.log', level=logging.INFO)

@app.route('/hello')
def hello():
    app.logger.info('Hello route accessed')
    return 'Hello!'

medium

A. A log entry with message 'Hello route accessed' at INFO level

B. No log will be written because app.logger is not configured

C. An error log because logging.basicConfig is missing a format

D. A warning log with message 'Hello route accessed'

Solution

1. Step 1: Check logging configuration

   logging.basicConfig sets INFO level and file 'app.log'.

2. Step 2: Analyze app.logger usage

   app.logger.info writes an INFO level log with given message.

3. Final Answer:

   A log entry with message 'Hello route accessed' at INFO level -> Option A

4. Quick Check:

   app.logger.info logs message at INFO [OK]

Hint: app.logger.info writes INFO logs if level allows [OK]

Common Mistakes:

• Assuming app.logger needs extra setup beyond basicConfig
• Confusing log levels INFO and WARNING
• Thinking format is mandatory for logging

4. You set up logging in Flask with logging.basicConfig(filename='app.log', level=logging.ERROR) but notice that INFO logs still appear in app.log. What is the likely cause?

medium

A. The file app.log is not writable

B. logging.basicConfig does not control log levels

C. app.logger.info() does not respect logging levels

D. The root logger level was set before basicConfig and overrides it

Solution

1. Step 1: Understand basicConfig behavior

   basicConfig only works if root logger has no handlers yet.

2. Step 2: Identify cause of wrong log levels

   If root logger was configured earlier, basicConfig call is ignored, so level stays lower.

3. Final Answer:

   The root logger level was set before basicConfig and overrides it -> Option D

4. Quick Check:

   Previous root logger config blocks basicConfig [OK]

Hint: basicConfig ignored if root logger already configured [OK]

Common Mistakes:

• Believing basicConfig cannot set levels
• Thinking app.logger ignores levels
• Assuming file permission causes wrong logs

5. You want to log errors and warnings to a file error.log and info messages to info.log in your Flask app. Which setup correctly achieves this?

hard

A. Use print statements instead of logging for info and error messages

B. Call logging.basicConfig twice with different filenames and levels

C. Use two handlers: one FileHandler for error.log with level WARNING, another for info.log with level INFO, added to app.logger

D. Set app.logger level to INFO and write all logs to error.log only

Solution

1. Step 1: Understand multiple log files need multiple handlers

   One handler per file with its own level filters logs accordingly.

2. Step 2: Check options for multiple handlers

   Use two handlers: one FileHandler for error.log with level WARNING, another for info.log with level INFO, added to app.logger correctly uses two FileHandlers with different levels added to app.logger.

3. Final Answer:

   Use two handlers: one FileHandler for error.log with level WARNING, another for info.log with level INFO, added to app.logger -> Option C

4. Quick Check:

   Multiple handlers = multiple log files [OK]

Hint: Use multiple handlers for different log files and levels [OK]

Common Mistakes:

• Calling basicConfig multiple times (only first works)
• Logging all levels to one file without filtering
• Using print instead of logging for production