spring-cloud / spring-cloud/spring-cloud-openfeign
Feign Client not auto-instrumented with Micrometer Tracing (OpenTelemetry) on Spring Cloud 2024.0.0
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.3k
- Forks
- 838
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 13
Description
I’m using Spring Boot 3.2.x and Spring Cloud 2024.0.0 (Leyton) with Micrometer Tracing and OpenTelemetry.
Expected behavior:
Feign clients should be automatically instrumented with TracingFeignClient, or at least propagate traceparent headers automatically.
Observed behavior:
Feign client is still a JDK dynamic proxy (jdk.proxy2.$Proxy...) and does not propagate tracing headers.
Only workaround is to inject headers manually via custom RequestInterceptor.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how Feign clients are created in Spring Cloud OpenFeign and how Micrometer Tracing integrates with OpenTelemetry. Compare the JDK proxy behavior with the expected TracingFeignClient path and inspect where traceparent propagation should occur. Done means Feign clients are automatically instrumented or propagate tracing headers without a custom RequestInterceptor.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring, spring-boot
- Domain
- api, backend, observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100