open telemetry - spring boot 3, with @Scheduled, and io.opentelemetry.instrumentation:opentelemetry-spring-boot-starter keep usi

Spring boot 3.4.2 with:

io.opentelemetry.instrumentation:opentelemetry-spring-boot-starter

Managed by:

mavenBom("io.opentelemetry:opentelemetry-bom:1.46.0")

and

mavenBom("io.opentelemetry.instrumentation:opentelemetry-instrumentation-bom-alpha:2.12.0-alpha")

When running the scheduled keep using same trace id:

@Scheduled(fixedRate = 10000)
public void callHero() {
    log.info("{}","hello")
}

The resulting output:

2025-02-03T19:48:43.423-06:00  INFO 43618 --- [a-otel] [   scheduling-1] [9252d302d75e48b8e25af53b6621647d-2916ce0fa2e97ab2]
2025-02-03T19:48:53.244-06:00  INFO 43618 --- [a-otel] [   scheduling-1] [9252d302d75e48b8e25af53b6621647d-d0b5bf23d13fd026]

Please suggest additional configuration for @Scheduled with opentelemetry.

Spring boot 3.4.2 with:

io.opentelemetry.instrumentation:opentelemetry-spring-boot-starter

Managed by:

mavenBom("io.opentelemetry:opentelemetry-bom:1.46.0")

and

mavenBom("io.opentelemetry.instrumentation:opentelemetry-instrumentation-bom-alpha:2.12.0-alpha")

When running the scheduled keep using same trace id:

@Scheduled(fixedRate = 10000)
public void callHero() {
    log.info("{}","hello")
}

The resulting output:

2025-02-03T19:48:43.423-06:00  INFO 43618 --- [a-otel] [   scheduling-1] [9252d302d75e48b8e25af53b6621647d-2916ce0fa2e97ab2]
2025-02-03T19:48:53.244-06:00  INFO 43618 --- [a-otel] [   scheduling-1] [9252d302d75e48b8e25af53b6621647d-d0b5bf23d13fd026]

Please suggest additional configuration for @Scheduled with opentelemetry.

• open-telemetry
• micrometer
• spring-boot-3
• open-telemetry-java

Share Improve this question Follow edited Feb 5 at 2:31 Samu Németh 57011 gold badge55 silver badges2020 bronze badges asked Feb 4 at 1:59 birbir 111 bronze badge

Add a comment  | 

1 Answer 1

Sorted by: Reset to default 0

Spring Framework's @Scheduled annotation is already instrumented, I think io.opentelemetry.instrumentation:opentelemetry-spring-boot-starter (not an official Spring Boot starter) might be conflicting with it.

I would recommend removing it and adding:

org.springframework.boot:spring-boot-starter-actuator
io.micrometer:micrometer-tracing-bridge-otel
io.opentelemetry:opentelemetry-exporter-otlp // ow whatever exporter you use (if any)