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

Rename prefix for Zipkin attributes from OT to OTel #967

Merged
merged 1 commit into from
Sep 21, 2020

Conversation

anuraaga
Copy link
Contributor

The official rename of the acronym happened after this spec was made, but looks like we haven't updated it yet.

@Oberon00
Copy link
Member

We should really standardize these attribute names across different exporters #660 (comment)

@anuraaga
Copy link
Contributor Author

Yeah definitely - I see work like open-telemetry/opentelemetry-python#1124 but should we block work on exporters until the attributes are finalized?

@Oberon00
Copy link
Member

No, I don't think that is required, as long as we take care to be consistent even without a central definition.

@Oberon00
Copy link
Member

I just did not approve because I have no idea about zipkin 😄

Copy link
Member

@tigrannajaryan tigrannajaryan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we should specify somewhere that "otel.*" is reserved for OpenTelemetry usage and should not be used for any other semantic conventions or attribute names. This is to ensure there are no clashes if the end users decide for some reason to prefix their own attributes with "otel.".

Can be done in a separate PR.

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

Successfully merging this pull request may close these issues.

8 participants