opentracing-contrib / opentracing-contrib/java-spring-cloud
Question: hystrix span creation under existing scope's span is not working
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 399
- Forks
- 143
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 22
Description
Hi everyone.
I instrumented my code with creating new span with help of io.opentracing.Scope class (jar version - 0.31.0). Then I added hystrix support with io.opentracing.contrib.spring.cloud.hystrix.TracedHystrixCommand (dependency opentracing-spring-cloud-hystrix-starter, version 0.2.2). I am using jaeger implementation of opentracing API (version 0.27.0).
The problem is that spans are showing in the UI separately, they are not the part of the same flow. Is that a standard behavior or I need to do some manipulations to get it working?
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 with io.opentracing.contrib.spring.cloud.hystrix.TracedHystrixCommand and reproduce the reported behavior using the versions listed in the issue. Inspect how the existing io.opentracing.Scope and Jaeger spans are related in the UI; done means confirming whether the Hystrix span joins the existing trace or documenting the standard behavior and required configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring-boot
- Domain
- distributed-systems, observability-sre
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100