Logging in production in Flask - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the main purpose of logging in production?

Logging in production helps track what the application is doing, find errors, and understand user behavior without stopping the app.

beginner

Which Python module is commonly used for logging in Flask applications?

The built-in logging module is commonly used for logging in Flask applications.

beginner

What is a log level and why is it important?

A log level shows how serious a message is (e.g., DEBUG, INFO, WARNING, ERROR). It helps filter messages so you see only what matters in production.

intermediate

How can you configure Flask to write logs to a file in production?

You can set up a FileHandler in the logging module to write logs to a file, and attach it to Flask's logger.

beginner

Why should you avoid logging sensitive information in production?

Logging sensitive data can expose private user info or secrets if logs are accessed by unauthorized people. It risks security and privacy.

Which log level should you use to record unexpected errors in production?

A INFO

B DEBUG

C WARNING

D ERROR

ERROR level is used to log serious problems that need attention in production.

What does the logging.FileHandler do in Flask logging?

A Sends logs to the console

B Filters logs by level

C Sends logs to a file

D Encrypts log messages

FileHandler writes log messages to a file.

Why is the DEBUG log level usually turned off in production?

A It shows too much detail and can slow down the app

B It hides important errors

C It only logs warnings

D It encrypts logs

DEBUG logs are very detailed and can clutter logs and affect performance in production.

Which of these is NOT a good practice for production logging?

A Logging sensitive user passwords

B Using appropriate log levels

C Writing logs to files

D Rotating log files to save space

Logging sensitive data like passwords is a security risk and should be avoided.

How can you make sure logs don’t fill up disk space in production?

A Only log errors

B Use log rotation to archive or delete old logs

C Disable logging completely

D Log everything at DEBUG level

Log rotation helps manage disk space by archiving or removing old logs.

Explain how to set up logging in a Flask app for production use.

Think about how to send logs to a file and control what messages appear.

Describe why managing log levels is important in production environments.

Consider what happens if you log too much or too little.

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