Micrometer Tracing instrumentation not working with Spring Boot 3.0

[samueldcs]

Describe the bug
Feign doesn't seem to be sending Trace/Span IDs as of Spring Boot 3.0.1.
Enabling logs reveals that none of the headers are being sent.

Sample
I've tried the examples on here and while they work, the headers aren't being propagated,

[antechrestos]

@samueldcs Hi

you may have missed the required dependency as specified in the documentation

MicrometerObservationCapability micrometerObservationCapability: If feign-micrometer is on the classpath and ObservationRegistry is available
MicrometerCapability micrometerCapability: If feign-micrometer is on the classpath, MeterRegistry is available and ObservationRegistry is not available

when the following dependency is added

        <dependency>
            <groupId>io.github.openfeign</groupId>
            <artifactId>feign-micrometer</artifactId>
        </dependency>

auto configuration FeignClientsConfiguration.MicrometerConfiguration gets activated and traces are propagated.

[bosofelipe]

@antechrestos Even with the dependency in my pom.xml, micrometer metrics isn´t enable properly, i need to add a bean to enable, like below

import feign.Capability;
import feign.micrometer.MicrometerCapability;
import io.micrometer.core.instrument.MeterRegistry;
import org.springframework.context.annotation.Bean;
import org.springframework.context.annotation.Configuration;

@Configuration
public class FeignMicrometerConfiguration {

  @Bean
  public Capability capability(final MeterRegistry registry) {
    return new MicrometerCapability(registry);
  }
}

Is a correct way to enable open feign micrometer metrics?

[samueldcs]

Adding Feign Micrometer didn't solve the issue, although I haven't faced @bosofelipe's problem - adding the dependency properly added the capability. Logging shows that headers are still not being propagated.

[masterj3y]

I have the same issue

[OlgaMaciaszek]

Hello @samueldcs thanks for submitting the issue and providing the sample. I have checked your sample for Zipkin. After adding the missing dependency, I get 2 spans generated for the call:

1. http get /github/contributors
2. http get, which is a child span of 1).
   This behaviour is analogous to the way it worked in 2021.x with spring-cloud-starter-sleuth and spring-cloud-sleuth-zipkin on the classpath (please see attached span json spans.log).
   If you're still experiencing an issue, please provide the steps to reproduce it in the sample or a different sample that reproduces the issue.
   CC @antechrestos @bosofelipe @masterj3y.

[samueldcs]

Hi @OlgaMaciaszek thanks for looking into this.
Upon further investigation, I found out that adding the micrometer capability dependency indeed instruments FeignClients.
However, I'm facing a weird problem where each span has a different TraceID. I suspected it had something to do with my reporter, but once I used RestTemplate with the same dependencies the spans were properly grouped. Later today I'll submit a sample with both clients.

[OlgaMaciaszek]

Thanks for the update, @samueldcs. Please provide the samples.