opentracing-contrib / opentracing-contrib/java-spring-cloud
Spring cloud context library in not appending span properly
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 399
- Forks
- 143
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 22
Description
Original issue: https://github.com/jaegertracing/jaeger-client-java/issues/381
Hi,
I have been using jaeger-core 0.24.0 version along with opentracing-spring-cloud-starter 0.1.1 version.
One of the library in our project uses spring-cloud-context version 1.3.2.RELEASE.
After using spring cloud context jar, we are not getting traces properly.
I am getting in downstream service span.
cc @chandresh-pancholi
Contributor guide
No contributing guide indexed for this repository
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 reviewing the linked original issue and the reported combination of jaeger-core 0.24.0, opentracing-spring-cloud-starter 0.1.1, and spring-cloud-context 1.3.2.RELEASE. Reproduce the missing downstream span and trace the affected Spring Cloud integration; done means the interaction is understood and spans are propagated correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- distributed-systems, observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100