open-telemetry / open-telemetry/opentelemetry-java
IdGenerator accept parameter when generate spanId or traceId
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 2.5k
- Forks
- 1k
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 58
Description
Is your feature request related to a problem? Please describe.
Now, SdkSpanBuidler.startSpan() call generateSpanId first, may call generateTraceId() next. Two id generate logic nothing to do with each other. It block all possiblity to generateTraceId derive from spanId generated previous.
opentelemetry-go's id_generator accept a traceID parameter when generate spanId. It is a ideal api definetion.
Describe alternatives you've considered
No other alternative method.
Additional context
related issue #4599
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 with SdkSpanBuidler.startSpan() and inspect the generateSpanId and generateTraceId entry points to understand their current ordering and relationship. Read related issue #4599 for context. Done means the ID generator API can receive the previously generated ID when generating the other ID, with the intended behavior covered by the project's relevant tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100