Application logging best practices

[aecordoba]

I'm newbie in Python development.
I was reading several logging tutorials. For example, in "Medium" you have this guide:
A Step-by-Step Guide to Configuring Python Logging with YAML Files
It suggests to load configuration file in order to log a message, this way:

import logging.config import yaml # Load the config file with open('logging_config.yaml', 'rt') as f: config = yaml.safe_load(f.read()) # Configure the logging module with the config file logging.config.dictConfig(config) # Get a logger object logger = logging.getLogger('development') # Log some messages logger.debug('This is a debug message')

But, when I have an application with several modules, I have to repeat this code in every module that need to log.
Are there any way to avoid this boilerplate?
Is there a solution in the standard library for this issue?

Thank you, in advance.
--
Adrián E. Córdoba

[snippsat]

Use logurur it has no or minimal boilerplate setup.
Example.

import time from loguru import logger logger.add("loop.log", rotation="1 week") start = logger.info('Start of loop') targets = ["a", "b", "c"] for target in targets: time.sleep(5) logger.debug(f"Log file: {target}") end = logger.info('End of loop')

Output:
2025-11-02 09:50:58.219 | INFO | __main__:<module>:5 - Start of loop 2025-11-02 09:51:03.221 | DEBUG | __main__:<module>:9 - Log file: a 2025-11-02 09:51:08.222 | DEBUG | __main__:<module>:9 - Log file: b 2025-11-02 09:51:13.223 | DEBUG | __main__:<module>:9 - Log file: c 2025-11-02 09:51:13.224 | INFO | __main__:<module>:10 - End of loop

For a application if build like a package can have the minimal setup in __init__.py at top level.
app/__init__.py:

from loguru import logger import sys # Only info to file logger.remove() logger.add("logs/app.log", rotation="10 MB")

Then your modules just log;
app/module_a.py:

from loguru import logger def run(): logger.debug("A says hi") 

app/module_b.py:

from loguru import logger def run(): logger.info("B reporting")