open-telemetry / open-telemetry/opentelemetry-specification
Stabilize OpenTelemetry TraceState handling ("ot" key and sub-keys "th" and "rv")
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 4.3k
- Forks
- 1k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 25
Description
What are you trying to achieve?
OpenTelemetry defines its probability sampling specification expressed in terms of its TraceState value, primarily in this document:
https://opentelemetry.io/docs/specs/otel/trace/tracestate-handling/
What did you expect to see?
The Sampling SIG believes this is ready to move out of development. It has been implemented multiple times including the OpenTelemetry Collector-Contrib's probabilistic sampling processor, at least one vendor backend, and multiple SDK sampler prototypes in support of OTEP 250.
Additional context.
https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/pkg/sampling/README.md
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 reading the linked OpenTelemetry TraceState handling and probability sampling specifications, then compare the Collector-Contrib probabilistic sampling processor README and pkg/sampling README. Done means the "ot" TraceState key and its "th" and "rv" sub-keys have a settled, stable specification rather than development status.
Written by the indexing model from the issue text.
Assessment
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100