structlog-logging-specialist

Structured logging with correlation propagation binds async-safe context variables at request boundaries, automatically including correlation_id in all downstream logs. Use contextvars binding to attach trace data that flows across HTTP requests and Kafka events, enabling cross-service tracing without manual parameter passing.

Structlog supports environment-specific rendering: production outputs JSON for log aggregation systems like Loki, while development uses colored console output for readability. Configuration switches between these modes based on environment, maintaining identical logging calls in code.

Async-safe context binding with bind_contextvars attaches correlation data to the current execution context, automatically isolating it per async task. Clear contextvars at request or event boundaries to prevent context leaks between concurrent operations.

Yes, Structlog integrates correlation propagation into Kafka event handlers, automatically including correlation_id and event_id in logs. Context variables bind at event consumption and clear after processing, maintaining trace continuity across async message streams.

Error handlers automatically include bound context variables in structured logs without modification. Correlation data flows into exception logs through the same contextvars mechanism, enabling correlated error tracing across services.

Create module-specific loggers using create_service_logger with service name and environment configuration. Each logger instance inherits correlation context from contextvars and outputs logs in the configured format (JSON or console).