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

Support reserving the namespace without specifying any attributes #1197

Open
lmolkova opened this issue Jun 28, 2024 · 0 comments
Open

Support reserving the namespace without specifying any attributes #1197

lmolkova opened this issue Jun 28, 2024 · 0 comments
Labels
enhancement New feature or request schema Semantic Conventions schema definition tooling Regarding build, workflows, build-tools, ...

Comments

@lmolkova
Copy link
Contributor

#1188 (comment)

There were similar attempts to reserve the namespace in the past and we should allow it.

It could also help with things like #713 (e.g. I want to add db.system=foo, this effectively means that db.foo.* namespace is reserved for attributes specific to this database)
@lmolkova lmolkova added tooling Regarding build, workflows, build-tools, ... schema Semantic Conventions schema definition labels Jun 28, 2024
@lmolkova lmolkova added the enhancement New feature or request label Jun 28, 2024
@lmolkova lmolkova mentioned this issue Jun 28, 2024
Merged
3 tasks
@lmolkova lmolkova moved this to Improve YAML Schema in Semantic Conventions Tooling Jul 24, 2024
CodeBlanch pushed a commit to CodeBlanch/semantic-conventions that referenced this issue Aug 16, 2024
@tigrannajaryan @jsuereth
Add guidance on when to use and not use nested namespaces (open-telem…
fb0804e 
…etry#1197)

This topic has come up at least 3 times now. I believe a clarification is
warranted. The clarification is aligned with previous recommendations:
open-telemetry/opentelemetry-specification#789 (comment)
open-telemetry/opentelemetry-specification#882 (comment)
open-telemetry/opentelemetry-specification#1194 (comment)
CodeBlanch pushed a commit to CodeBlanch/semantic-conventions that referenced this issue Aug 16, 2024
@tigrannajaryan @jsuereth
Add guidance on when to use and not use nested namespaces (open-telem…
82b14e1 
…etry#1197)

This topic has come up at least 3 times now. I believe a clarification is
warranted. The clarification is aligned with previous recommendations:
open-telemetry/opentelemetry-specification#789 (comment)
open-telemetry/opentelemetry-specification#882 (comment)
open-telemetry/opentelemetry-specification#1194 (comment)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request schema Semantic Conventions schema definition tooling Regarding build, workflows, build-tools, ...
Projects
Semantic Conventions Tooling
Status: Improve YAML Schema (Long-Term)
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jsuereth @lmolkova