Logging & Structured Observability

Expert Answer & Key Takeaways

Mastering Logging & Structured Observability is essential for high-fidelity technical performance and advanced exam competency in 2026.

Logging & Structured Observability: Beyond the Print Statement (2026)

Logging is the primary way to understand what your application is doing in production. Moving beyond print() to the standard logging module allows for level-based filtering, multiple destinations (handlers), and structured data output.

1. The Proof Code (Professional Logger Setup)

import logging
import sys

# 1. Basic Configuration
logging.basicConfig(
    level=logging.INFO,
    format="%(asctime)s [%(levelname)s] %(name)s: %(message)s",
    handlers=[
        logging.StreamHandler(sys.stdout), # Console
        logging.FileHandler("app.log")     # Persistent File
    ]
)

logger = logging.getLogger("AuthService")

def login_user(username: str):
    logger.info(f"Login attempt for user: {username}")
    try:
        # Simulate failure
        1 / 0
    except Exception:
        logger.exception("Login failed due to internal error") # Automatically includes Traceback

if __name__ == "__main__":
    login_user("admin")

2. Execution Breakdown

Log Levels: Standardize the importance of messages (DEBUG, INFO, WARNING, ERROR, CRITICAL). In production, you typically set the level to INFO or WARNING to reduce noise.
Handlers: Determine where the logs go. Common handlers include StreamHandler (terminal), FileHandler (local disk), and HTTPHandler (remote log server).
Formatters: Define the structure of the log line. In 2026, many production systems use JSON Formatters so that logs can be easily parsed by tools like ELK (Elasticsearch) or Datadog.
logger.exception(): A specialized method for except blocks that automatically attaches the full stack trace to the log message, saving hours of debugging time.

3. Detailed Theory

Logging is about providing context for future-you when things go wrong at 3 AM.

The Logger Hierarchy

Loggers are hierarchical (app.database, app.ui). You can configure the root logger once, and all sub-loggers will inherit its settings unless overridden. This allows you to turn on DEBUG logs for just one specific module without flooding the entire system.

Structured Logging (JSON)

Instead of plain text: User logged in: admin, structured logging produces: {"event": "login", "user": "admin", "status": "success"}. This allows you to run complex queries like 'Show me all failed logins for user X in the last 10 minutes'.

Thread & Process Safety

The standard logging module is thread-safe. However, if you are logging to the same file from multiple processes, you need to use a specialized QueueHandler or an external logging service to prevent file corruption.

[!TIP] Senior Secret: Avoid 'f-string logging' for variable data. Instead of logger.info(f"User {name} logged in"), use logger.info("User %s logged in", name). This is more efficient because the string interpolation only happens if the log level is actually enabled. If INFO is disabled, the interpolation never runs, saving CPU cycles in hot paths.

Logging & Structured Observability

Expert Answer & Key Takeaways