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.

Sign up for GitHub

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

Jump to bottom

Semantic convention namespacing recommendations #585

Open
tigrannajaryan opened this issue May 5, 2020 · 1 comment
Open

Semantic convention namespacing recommendations #585

tigrannajaryan opened this issue May 5, 2020 · 1 comment
Labels
area:semantic-conventions Related to semantic conventions release:after-ga Not required before GA release, and not going to work on before GA

Comments

@tigrannajaryan
Copy link
Member

There is currently no defined process for coming up with new sub-namespaces (such as "k8s") for semantic conventions and no recommendations for naming custom attributes.

We want to come up with a process for adding sub-namespaces that is flexible, fast and easy for the entire industry to contribute, yet ensures there are no name collisions.

We also want to come up with recommendation for custom attribute naming. Decide how application developers can ensure their custom attributes don't conflict with common attributes, including attributes that will be added to the conventions after the application is released (for example, can we recommend reverse domain name notation?).
@tigrannajaryan tigrannajaryan mentioned this issue May 5, 2020
Open
@carlosalberto
Copy link
Contributor

We also want to come up with recommendation for custom attribute naming. Decide how application developers can ensure their custom attributes don't conflict with common attributes

+1

@reyang reyang added the area:semantic-conventions Related to semantic conventions label Jun 26, 2020
@reyang reyang added the release:after-ga Not required before GA release, and not going to work on before GA label Jul 6, 2020
@jsuereth jsuereth mentioned this issue Aug 26, 2022
Closed
@bertysentry bertysentry mentioned this issue Mar 27, 2023
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area:semantic-conventions Related to semantic conventions release:after-ga Not required before GA release, and not going to work on before GA
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@carlosalberto @tigrannajaryan @reyang