db.operation.name
The name of the operation or command being executed.
It is RECOMMENDED to capture the value as provided by the application without attempting to do any case normalization.
The operation name SHOULD NOT be extracted from db.query.text,
when the database system supports query text with multiple operations
in non-batch operations.
If spaces can occur in the operation name, multiple consecutive spaces SHOULD be normalized to a single space.
For batch operations, if the individual operations are known to have the same operation name
then that operation name SHOULD be used prepended by BATCH ,
otherwise db.operation.name SHOULD be BATCH or some other database
system specific term if more applicable.
Examples
- findAndModify
- HMSET
- SELECT
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 (21)
- span.azure.cosmosdb.client
- span.azure.cosmosdb.client *
- span.db.cassandra.client
- span.db.cassandra.client
- span.db.client
- span.db.client
- span.db.couchdb.client
- span.db.elasticsearch.client
- span.db.elasticsearch.client *
- span.db.hbase.client
- span.db.hbase.client *
- span.db.mariadb.client
- span.db.mongodb.client
- span.db.mongodb.client *
- span.db.mysql.client
- span.db.oracledb.client
- span.db.postgresql.client
- span.db.redis.client
- span.db.redis.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).