What are you trying to achieve?
Semantic convention for db client calls (database.md) states that for db.name "the database name to be used is the more specific layer". This may cause problems because as a user I don't know beforehand what the tag actually describes. For one db engine the tag may describe the "schema name" and for another a "database name".
This approach also makes it difficult to distinguish e.g. between two schemas with the same schema name running under two different instances.
I believe that db.name should behave consistently regardless of the database engine used (always store "database name"). Moreover it might be helpful to add more tags to describe database-specific layers (like db.schema_name or something similar).
Additional context.
https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/semantic_conventions/database.md
What are you trying to achieve?
Semantic convention for db client calls (database.md) states that for
db.name"the database name to be used is the more specific layer". This may cause problems because as a user I don't know beforehand what the tag actually describes. For one db engine the tag may describe the "schema name" and for another a "database name".This approach also makes it difficult to distinguish e.g. between two schemas with the same schema name running under two different instances.
I believe that
db.nameshould behave consistently regardless of the database engine used (always store "database name"). Moreover it might be helpful to add more tags to describe database-specific layers (likedb.schema_nameor something similar).Additional context.
https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/semantic_conventions/database.md