Restoring Quartz Job Log Tracing After Migrating to Spring Boot 3+

Alexander Kanenkov from Domclick addresses a common issue encountered when migrating services to Spring Boot 3+: Quartz jobs lose their traceId, resulting in a loss of observability in logs. The article explains why trace context is lost in worker threads, preventing developers from linking background tasks to the HTTP requests that triggered them. The author provides a step-by-step guide to fixing this issue, ensuring that tracing works correctly for both in-memory (RAM) and JDBC job stores. This solution restores system observability by properly correlating background tasks with their parent requests, which is essential for debugging distributed applications. This guide is highly relevant for backend developers facing similar challenges during Spring stack upgrades.