Module-level loggers let a package share central logging configuration without each module changing the root logger.
Understanding the Concept
Module-level loggers let a package share central logging configuration without each module changing the root logger. Names such as app.db and app.api are easy to filter separately.
Propagation is useful when configured once; repeated handlers often explain duplicated log lines.
How this helps diagnose real applications
First decide what question you are trying to answer: whether a particular branch runs, why an operation failed, or what contextual event should be recorded. Logging, interactive debugging, traceback inspection and controlled timing complement each other but produce different kinds of evidence.
Diagnostic output should preserve enough context to reproduce the problem without recording passwords, tokens, full personal records or untrusted payloads. Keep instrumentation focused so it does not hide the original behavior.
Worked Example
Read the code from the first line to the last. Identify which values are inputs, which operation is being demonstrated and what should happen before running it.
import logging
logging.basicConfig(level=logging.INFO, format="%(name)s:%(message)s")
api_logger = logging.getLogger("app.api")
db_logger = logging.getLogger("app.db")
api_logger.info("Request accepted")
db_logger.info("Record saved")Walkthrough: What Each Part Does
- The imports make logging available. These are standard-library building blocks unless the example explicitly names an external tool.
- Observe which message or diagnostic field appears and which condition caused it. Modify the input deliberately to test the failure path.
This demonstration focuses on one practical behavior. Before changing several lines, vary one input or one configuration choice and check whether the result changes for the reason you expected.
The example completed in the local test environment. Its output is not fixed enough to publish as a universal expected result; inspect the result on your own computer.
Important Behavior and Edge Cases
Calling basicConfig inside each imported module or attaching duplicate handlers to child and parent loggers.
Propagation is useful when configured once; repeated handlers often explain duplicated log lines.
Practice Exercise
Configure app.db at WARNING while leaving app.api at INFO, then compare visible messages.
Write down the result you expect before running your changed code. Check at least one normal case and one boundary or failure case. If your example starts workers or opens resources, verify how they are cleaned up.
Further reading: official documentation and API reference.
Common Beginner Mistakes
- Calling basicConfig inside each imported module or attaching duplicate handlers to child and parent loggers.
- Removing the diagnostic message after seeing it once instead of reproducing the failure and checking the underlying cause.
Key Takeaways
- Module-level loggers let a package share central logging configuration without each module changing the root logger.
- Propagation is useful when configured once; repeated handlers often explain duplicated log lines.
- Practice: Configure app.db at WARNING while leaving app.api at INFO, then compare visible messages.