The 30 second answer
You cannot stitch one request's logs across services, so debugging becomes timestamp guessing and mean time to recover goes up. Use distributed tracing with W3C traceparent propagation. In Spring Boot, Micrometer Tracing with an OpenTelemetry or Brave bridge propagates trace and span ids through instrumented clients and puts them in the log MDC. Centralize logs and return the trace id to clients on errors.
You can't stitch one request's logs across services — debugging is timestamp guessing, slow MTTR. Fix: distributed tracing with W3C traceparent propagation; in Spring Boot, Micrometer Tracing (OTel or Brave bridge) auto-propagates trace/span ids through instrumented clients and adds them to the log pattern (MDC); centralize logs; return the trace id to clients in error responses.
Sources: