open-telemetry / open-telemetry/opentelemetry-python
Little confused about B3MultiFormat key name spell
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.6k
- Forks
- 1k
- Avg merge
- 4d 15h
- Merged PRs (30d)
- 19
Description
According to the description in the protocol https://github.com/openzipkin/b3-propagation, there does not seem to be any specification around letter case for those keys.
However, based on experience, the opentelemetry java sdk / npm sdk and former opentracing (jaeger) have implemented them in a case-sensitive way.
This brings about some issues around lack of consistency, meaning additional work is needed to unify things.
I'd like to ask if anyone has any suggestions or experience regarding this?
Or if possible, can I try changing them into a capitalized form similar to these SDKs?
Please let me know if I have accurately conveyed the key points you wanted to get across or if any part needs clarification or improvement. I'm happy to incorporate any feedback to refine the translation.
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 comparing the B3 protocol description with the OpenTelemetry Java B3Propagator.java implementation and the npm B3 propagator linked in the issue. Confirm how each implementation treats key casing, then document the proposed behavior and identify the Python changes and compatibility expectations once maintainers decide on a direction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100