How would you design structured logging and correlation in a Spring Boot service?

I define a small log event schema with service version, environment, event name, severity, outcome, and correlation fields, then verify the log pipeline preserves types and multiline exceptions. Sampling or suppression targets high-volume success events, not rare failures needed for diagnosis. Async execution carries MDC through supported context propagation and clears it afterward. Retention, access, and redaction are part of the design because searchable structured data increases both operational value and privacy risk.