Make initial traceparent optional
Open
Nobody has claimed this yet.
revisit-later
- Dominant language
- Python
- Stars
- 510
- Forks
- 80
- PR merge metrics
- No merged PRs in 30d
Description
There are a number of reasons why initial headers sent should allow tracestate without traceparent.
- format or vendor-specific sampling hints. ex
b3=1 - passing in a format or vendor-specific way only the trace ID
- vendors who are only using tracestate for non-trace data such as appId
- special, vendor-specific instructions. ex return back a synthetic parent ID
- mechanical conversion of existing headers by a proxy
- ex stashing the b3 header as a b3 entry, as a save point, but without having to convert it to traceparent format which has a squishy notion of the sampling flag.
Most importantly, this can help reduce the pressure to add vendor-specific features to the traceparent or response variants.
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
The issue names no files, tests, or entry points. Start by reviewing the Trace Context handling for initial headers and determine the specification change needed to permit tracestate without traceparent. Done means the proposed behavior and interoperability implications are precise enough for the project to assess.
Written by the indexing model from the issue text.
Assessment
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100