Скачать или смотреть How to Manage Parent and Child Logger Levels in Python's Logging Module

Discover how to effectively configure parent and child loggers in Python to manage logging levels for your applications without losing important debug information.
---
This video is based on the question https://stackoverflow.com/q/67054217/ asked by the user 'Ohad Shemesh' ( https://stackoverflow.com/u/11135233/ ) and on the answer https://stackoverflow.com/a/67054344/ provided by the user 'Masklinn' ( https://stackoverflow.com/u/8182118/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: Parent logger with level lower than child's

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
How to Manage Parent and Child Logger Levels in Python's Logging Module: A Complete Guide

In the realm of Python logging, many developers encounter challenges when trying to configure loggers in a hierarchical manner. One common issue arises when a parent logger has a lower log level than its child logger. This can lead to unwanted behavior where debug logs from child modules are still emitted, even when you only want higher-level logs. In this guide, we will explore how to manage logging levels effectively in your Python applications.

The Problem: Parent Logger with a Lower Level than Child

It’s a standard practice for Python packages to define a top-level logger and have every sub-module create its own "child" logger using the convention:

[[See Video to Reveal this Text or Code Snippet]]

In certain scenarios, you may find yourself wanting to disable DEBUG logs from a specific child module (for example, package.module) while maintaining a DEBUG level for the overall package.

For instance, you may try the following configuration:

[[See Video to Reveal this Text or Code Snippet]]

While this seems logical, the DEBUG logs still propagate from the child logger due to the parent logger's configuration, leading to confusion.

Solution: Effective Logger Configuration

To effectively control logging levels for both parent and child loggers, we can employ a systematic approach:

Step 1: Logger Configuration

You can use the logging.config.dictConfig() method, as shown below, to set up your loggers:

[[See Video to Reveal this Text or Code Snippet]]

Step 2: Log Messages

Now, when you log a message from both the parent and child loggers:

[[See Video to Reveal this Text or Code Snippet]]

The output will show that the debug message from the parent logger is emitted while the child logger's debug message does not appear.

Understanding Log Level Propagation

The behavior you observe is rooted in how Python's logging system manages levels:

Loggers filter messages at intake. A logger will ignore a message if its logging level is below the logger's effective level.

The effective level of a logger is determined by checking the logger’s level and traversing up to the root logger until a defined level is found. If none is found, it defaults to NOTSET, resulting in all messages being emitted.

Important Note on Descendant Loggers

It's crucial to remember that if child loggers of package.module are set back to DEBUG, they will override the INFO setting. The log level is considered an intake filter—once a record is accepted, the logger’s level no longer affects it.

Different Use of the propagate Attribute

The propagate attribute serves a different purpose. It is primarily used to determine whether a logger should forward its messages to the parent logger's handlers. Setting propagate to False will block all logs to the parent, which is not always desirable if you still want logs at higher levels.

Conclusion

Managing logging levels effectively in a hierarchical logger setup can enhance your application's debugging capabilities while preventing unnecessary noise in your logs. By carefully configuring your logger settings and understanding how log levels propagate, you can ensure that only the necessary log messages are emitted.

With these guidelines in mind, you can enhance your logging strategy in Python, making it easier to maintain and debug your applications.