db.namespace
Stablestringas of v1.44.0
The name of the database, fully qualified within the server address and port.
If a database system has multiple namespace components, they SHOULD be concatenated from the most general to the most specific namespace component, using | as a separator between the components. Any missing components (and their associated separators) SHOULD be omitted.
Semantic conventions for individual database systems SHOULD document what db.namespace means in the context of that system.
It is RECOMMENDED to capture the value as provided by the application without attempting to do any case normalization.
Examples
- customers
- test.users
Used by
metrics (4)
- azure.cosmosdb.client.operation.request_charge
- db.client.cosmosdb.operation.request_charge
- db.client.operation.duration
- db.client.response.returned_rows
spans (19)
- span.azure.cosmosdb.client
- span.db.cassandra.client
- span.db.client
- span.db.couchdb.client
- span.db.elasticsearch.client
- span.db.hbase.client
- span.db.mariadb.client
- span.db.mariadb.client
- span.db.mongodb.client
- span.db.mysql.client
- span.db.mysql.client
- span.db.oracledb.client
- span.db.oracledb.client
- span.db.postgresql.client
- span.db.postgresql.client
- span.db.redis.client
- span.db.sql_server.client
- span.db.sql_server.client
- span.db.sql.client
* required on that signal.
History
- v1.33.0stability
Promoted to stable.
Already present at v1.30.0, the oldest release tracked here (release_candidate).