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

Improve wording of `db.collection.name` and `db.operation.name` (#2186)

This commit is contained in:
Trask Stalnaker 2025-04-28 07:38:29 -07:00 committed by GitHub
parent 7867bc07fa
commit 14f5330922
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
6 changed files with 24 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/attributes-registry/db.md
View File

@ -32,7 +32,8 @@ This group defines the attributes used to describe telemetry in the context of d
without attempting to do any case normalization.
The collection name SHOULD NOT be extracted from `db.query.text`,
when the database system supports cross-table queries in non-batch operations.
when the database system supports query text with multiple collections
in non-batch operations.
For batch operations, if the individual operations are known to have the same
collection name then that collection name SHOULD be used.
@ -47,7 +48,8 @@ It is RECOMMENDED to capture the value as provided by the application without at
without attempting to do any case normalization.
The operation name SHOULD NOT be extracted from `db.query.text`,
when the database system supports cross-table queries in non-batch operations.
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.

3
docs/database/cassandra.md
View File

@ -75,7 +75,8 @@ It is RECOMMENDED to capture the value as provided by the application without at
without attempting to do any case normalization.
The operation name SHOULD NOT be extracted from `db.query.text`,
when the database system supports cross-table queries in non-batch operations.
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.

3
docs/database/cosmosdb.md
View File

@ -374,7 +374,8 @@ Explaining bucket configuration:
without attempting to do any case normalization.
The operation name SHOULD NOT be extracted from `db.query.text`,
when the database system supports cross-table queries in non-batch operations.
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.

12
docs/database/database-metrics.md
View File

@ -101,7 +101,8 @@ of `[ 0.001, 0.005, 0.01, 0.05, 0.1, 0.5, 1, 5, 10 ]`.
without attempting to do any case normalization.
The collection name SHOULD NOT be extracted from `db.query.text`,
when the database system supports cross-table queries in non-batch operations.
when the database system supports query text with multiple collections
in non-batch operations.
For batch operations, if the individual operations are known to have the same
collection name then that collection name SHOULD be used.
@ -116,7 +117,8 @@ It is RECOMMENDED to capture the value as provided by the application without at
without attempting to do any case normalization.
The operation name SHOULD NOT be extracted from `db.query.text`,
when the database system supports cross-table queries in non-batch operations.
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.
@ -279,7 +281,8 @@ Explaining bucket configuration:
without attempting to do any case normalization.
The collection name SHOULD NOT be extracted from `db.query.text`,
when the database system supports cross-table queries in non-batch operations.
when the database system supports query text with multiple collections
in non-batch operations.
For batch operations, if the individual operations are known to have the same
collection name then that collection name SHOULD be used.
@ -294,7 +297,8 @@ It is RECOMMENDED to capture the value as provided by the application without at
without attempting to do any case normalization.
The operation name SHOULD NOT be extracted from `db.query.text`,
when the database system supports cross-table queries in non-batch operations.
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.

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

@ -124,7 +124,8 @@ classify as errors.
without attempting to do any case normalization.
The collection name SHOULD NOT be extracted from `db.query.text`,
when the database system supports cross-table queries in non-batch operations.
when the database system supports query text with multiple collections
in non-batch operations.
For batch operations, if the individual operations are known to have the same
collection name then that collection name SHOULD be used.
@ -139,7 +140,8 @@ It is RECOMMENDED to capture the value as provided by the application without at
without attempting to do any case normalization.
The operation name SHOULD NOT be extracted from `db.query.text`,
when the database system supports cross-table queries in non-batch operations.
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.

6
model/database/registry.yaml
View File

@ -14,7 +14,8 @@ groups:
without attempting to do any case normalization.
The collection name SHOULD NOT be extracted from `db.query.text`,
when the database system supports cross-table queries in non-batch operations.
when the database system supports query text with multiple collections
in non-batch operations.
For batch operations, if the individual operations are known to have the same
collection name then that collection name SHOULD be used.
@ -45,7 +46,8 @@ groups:
without attempting to do any case normalization.
The operation name SHOULD NOT be extracted from `db.query.text`,
when the database system supports cross-table queries in non-batch operations.
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.