palantir / palantir/tracing-java
Support undecided observability state
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 28
- Forks
- 20
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 15
Description
The default sampler should not cause a local service to observe operations, but it should also not prevent upstream tracing-aware services from recording trace data based on their local sampler configuration. This requires samplers to support an additional undecided state in addition to observed, and not observed.
In practice this should prevent the X-B3-Sampled from being set on outgoing requests.
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 locating the sampler state definitions and the code that sets the X-B3-Sampled header on outgoing requests. Trace how the default sampler and upstream tracing-aware services use these values. Done means samplers support observed, not observed, and undecided states, with undecided preventing the outgoing header from being set while preserving upstream sampling decisions.
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