Trace context not propagating between microservices using micrometer with openfeign

Question

My structure log is Logstash, and I see my trace ID in every microservice log. However, my trace ID is not the same in all requests between microservices. How can I ensure that trace context (traceparent/baggage) is automatically propagated when using OpenFeign in Spring Boot 3.4 with Micrometer and OpenTelemetry?

All microservices have these dependencies:

      <dependency>
        <groupId>io.micrometer</groupId>
        <artifactId>micrometer-tracing-bridge-otel</artifactId>
    </dependency>
    <dependency>     
        <groupId>io.opentelemetry</groupId>
        <artifactId>opentelemetry-exporter-otlp</artifactId>
    </dependency>
   <dependency>
      <groupId>org.springframework.cloud</groupId>
      <artifactId>spring-cloud-starter-openfeign</artifactId>
    </dependency>

my spring property config:

management:
  tracing:
    sampling:
      probability: 1.0 # report 100% of traces

Consider adding more relevant code to allow people to spot potential errors in the setup — Gordon
– Gordon, Commented May 14 at 8:43

RedComet · Accepted Answer · 2025-05-15 09:48:23Z

0

management:
  tracing:
    enabled: true
    propagation:
      type: W3C

in your configuration tells Spring Boot with Micrometer and OpenTelemetry to automatically propagate the tracing context across services, including Feign client calls.

answered May 15 at 9:48

RedComet

1

Sign up to request clarification or add additional context in comments.

1 Comment

Mehrdad Bozorgmehr May 15 at 16:49

The default propagation type of OpenTelemetry is W3C; I think it doesn't need to be set.

Collectives™ on Stack Overflow

Trace context not propagating between microservices using micrometer with openfeign

1 Answer 1

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related