Why logging.info Doesn't Output to Console and How to Fix It in Python

Default Configuration of Python Logging System

In Python's logging module, the logging system employs a flexible level mechanism to control the output of messages with varying severities. By default, the root logger is set to the WARNING level. This means that only log messages with a level equal to or higher than WARNING will be processed and output to configured handlers, such as the console.

Log Level Hierarchy and Default Behavior

Python defines the following standard log levels in increasing severity: DEBUG, INFO, WARNING, ERROR, and CRITICAL. Since the INFO level is lower than WARNING, messages generated by logging.info() calls are filtered out when the root logger level is WARNING, and thus do not appear on the console. In contrast, logging.warn() (or logging.warning()) and logging.error() have levels equal to or above WARNING, so they output normally.

Solution: Adjusting the Log Level

To make info-level log messages visible on the console, the root logger's level needs to be lowered to INFO or below. This can be achieved through two main methods, avoiding the need to modify each Python file individually.

Method 1: Direct Setting with setLevel()

As shown in the best answer, calling logging.getLogger().setLevel(logging.INFO) takes effect immediately. Here, logging.getLogger() retrieves the root logger instance, and the setLevel() method sets its level to INFO. Example code:

import logging
logging.getLogger().setLevel(logging.INFO)
logging.info('This message will now appear on the console')
logging.warn('Warning message also appears')

After execution, the console will output two log lines because the INFO level allows messages at info and higher levels to pass through.

Method 2: Configuration with basicConfig

Another approach is to use the logging.basicConfig() function, which offers a more comprehensive configuration method, allowing simultaneous setting of level, format, and handlers. For example:

import logging
logging.basicConfig(level=logging.DEBUG)
logging.info('info-level log is visible')
logging.debug('debug-level log is also visible')

Here, the level is set to DEBUG, the lowest level, so logs at all levels will be output. basicConfig() is typically called once at program startup and affects the entire logging system.

Advanced Topics and Best Practices

In real-world projects, it is recommended to dynamically set the log level via environment variables or configuration files to adapt to different environments (e.g., development, testing, production). For instance, use os.getenv() to read environment variables:

import logging
import os

level_name = os.getenv('LOG_LEVEL', 'WARNING')
level = getattr(logging, level_name.upper(), logging.WARNING)
logging.basicConfig(level=level)

logging.info('Output configured based on environment variable')

Furthermore, understanding the inheritance of log levels is crucial: child loggers can inherit level settings from parent loggers but can also override them. Proper use of logger hierarchies enhances the flexibility of log management.

Conclusion

The root cause of logging.info() not outputting to the console is the default WARNING level of the root logger. By lowering the level with setLevel() or basicConfig(), this issue can be resolved. Mastering these techniques helps developers efficiently utilize Python's logging system for debugging and monitoring.