You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your change request related to a problem? Please describe.
As we approach stability, I wanted to throw out a question of whether we should rename db.system to db.system.name in order to preserve the ability to use db.system as a namespace.
I don't see any need to include other db.system.* attributes on metrics / spans. But supposing semantic conventions expand to database servers (e.g. resource conventions to represent a database server), its possible we might want to include other attributes along the lines of db.system.version.
Describe the solution you'd like
Consider renaming db.system to db.system.name.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Area(s)
area:db
Is your change request related to a problem? Please describe.
As we approach stability, I wanted to throw out a question of whether we should rename
db.system
todb.system.name
in order to preserve the ability to usedb.system
as a namespace.I don't see any need to include other
db.system.*
attributes on metrics / spans. But supposing semantic conventions expand to database servers (e.g. resource conventions to represent a database server), its possible we might want to include other attributes along the lines ofdb.system.version
.Describe the solution you'd like
Consider renaming
db.system
todb.system.name
.Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: