open-telemetry
/
semantic-conventions
mirror of https://github.com/open-telemetry/semantic-conventions.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Update missing modification from `db.operation` to `db.operation.name` (#912)

This commit is contained in:
Steve Rao 2024-04-09 10:54:58 +08:00 committed by GitHub
parent 49669266d9
commit ccb6db6f3d
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/database/database-spans.md
View File

@ -55,7 +55,7 @@ The **span name** SHOULD be set to a low cardinality value representing the stat
It MAY be a stored procedure name (without arguments), DB statement without variable arguments, operation name, etc.
Since SQL statements may have very high cardinality even without arguments, SQL spans SHOULD be named the
following way, unless the statement is known to be of low cardinality:
`<db.operation.name> <db.name>.<db.collection.name>`, provided that `db.operation` and `db.collection.name` are available.
`<db.operation.name> <db.name>.<db.collection.name>`, provided that `db.operation.name` and `db.collection.name` are available.
If `db.collection.name` is not available due to its semantics, the span SHOULD be named `<db.operation.name> <db.name>`.
It is not recommended to attempt any client-side parsing of `db.statement` just to get these properties,
they should only be used if the library being instrumented already provides them.