open-telemetry / open-telemetry/opentelemetry-python
API sets tracecontext, baggage as default global propagators
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.6k
- Forks
- 1k
- Avg merge
- 4d 15h
- Merged PRs (30d)
- 19
Description
This behavior is in direct conflict with the API specification:
The OpenTelemetry API MUST use no-op propagators unless explicitly configured otherwise.
I think the SDK could do that, but not the API.
Side note: I find such logic in init violating the style guide: https://google.github.io/styleguide/pyguide.html#25-global-variables
Origin: Found by @Aneurysm9 when discussing https://github.com/open-telemetry/opentelemetry-go/issues/2611
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
Read opentelemetry-api/src/opentelemetry/propagate/init.py at lines 124-146, then compare its global-propagator behavior with the linked API specification. The change is complete when the API uses no-op propagators unless explicitly configured, without shifting SDK behavior into the API.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100