wide-event-logging

Wide-event-logging aggregates Spring Boot request events into a single JSON log by binding a per-request identifier using MDC and ThreadLocal, collecting events across controllers and domain logic, then outputting the final structured log with cleanup.

Wide event logging is the collection of all events generated during a single request into a unified JSON log. You need it to improve traceability and performance analysis across the entire processing pipeline in Spring Boot applications.

To trace a single request across layers, you capture and attach a per-request ID using MDC and ThreadLocal, enabling the aggregation of events from the controller, use case, domain, and infrastructure into one structured log.

Yes, this approach requires MDC and ThreadLocal usage to bind per-request identifiers, ensuring all events during the request lifecycle are correctly tracked and aggregated before final JSON output and cleanup.

The best way to output structured JSON logs for aggregation platforms is to collect all per-request events across your Spring Boot application layers and aggregate them into a single unified JSON log entry.

MDC ThreadLocal cleanup matters because failing to clear per-request identifiers after outputting the aggregated JSON log can cause memory leaks and cross-request data contamination in Spring Boot applications.