Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Little confused about B3MultiFormat key name spell #3598

Open
Liubey opened this issue Dec 21, 2023 · 0 comments
Open

Little confused about B3MultiFormat key name spell #3598

Liubey opened this issue Dec 21, 2023 · 0 comments

Comments

@Liubey
Copy link

Liubey commented Dec 21, 2023

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant