We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
In open-telemetry/opentelemetry-specification#3782 it was brought up that the (de-facto) case sensitivity of attribute keys is not documented. A clarification on that will likely be added to the spec (open-telemetry/opentelemetry-specification#3784).
In our attribute naming guidelines at https://github.com/open-telemetry/semantic-conventions/blob/main/docs/general/attribute-naming.md#attribute-naming, we do not cover casing. It is implied to some extent since all examples are lowercase and so are all currently defined keys in semantic conventions, but we might want to call that out explicitly.
The text was updated successfully, but these errors were encountered:
I opened a PR for it #788
Sorry, something went wrong.
AlexanderWert
Successfully merging a pull request may close this issue.
In open-telemetry/opentelemetry-specification#3782 it was brought up that the (de-facto) case sensitivity of attribute keys is not documented. A clarification on that will likely be added to the spec (open-telemetry/opentelemetry-specification#3784).
In our attribute naming guidelines at https://github.com/open-telemetry/semantic-conventions/blob/main/docs/general/attribute-naming.md#attribute-naming, we do not cover casing. It is implied to some extent since all examples are lowercase and so are all currently defined keys in semantic conventions, but we might want to call that out explicitly.
The text was updated successfully, but these errors were encountered: