forked from open-telemetry/semantic-conventions
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
3 changed files
with
36 additions
and
23 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -17,17 +17,18 @@ | |
|
|
||
| This group defines the attributes used to describe telemetry in the context of databases. | ||
|
|
||
| | Attribute | Type | Description | Examples | Stability | | ||
| | -------------------------------- | ------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------- | ---------------------------------------------------------------- | | ||
| | `db.client.connection.pool.name` | string | The name of the connection pool; unique within the instrumented application. In case the connection pool implementation doesn't provide a name, instrumentation should use a combination of parameters that would make the name unique, for example, combining attributes `server.address`, `server.port`, `username` and `database`, formatted as `[email protected]:server.port/database`. | `myDataSource` |  | | ||
| | `db.client.connection.state` | string | The state of a connection in the pool | `idle` |  | | ||
| | `db.collection.name` | string | The name of a collection (table, container) within the database. [1] | `public.users`; `customers` |  | | ||
| | `db.namespace` | string | The name of the database, fully qualified within the server address and port. [2] | `customers`; `test.users` |  | | ||
| | `db.operation.batch.size` | int | The number of queries included in a [batch operation](/docs/database/database-spans.md#batch-operations). [3] | `2`; `3`; `4` |  | | ||
| | `db.operation.name` | string | The name of the operation or command being executed. [4] | `findAndModify`; `HMSET`; `SELECT` |  | | ||
| | `db.query.parameter.<key>` | string | A query parameter used in `db.query.text`, with `<key>` being the parameter name, and the attribute value being a string representation of the parameter value. [5] | `someval`; `55` |  | | ||
| | `db.query.text` | string | The database query being executed. [6] | `SELECT * FROM wuser_table where username = ?`; `SET mykey "WuValue"` |  | | ||
| | `db.system` | string | The database management system (DBMS) product as identified by the client instrumentation. [7] | `other_sql`; `adabas`; `cache` |  | | ||
| | Attribute | Type | Description | Examples | Stability | | ||
| | ---------------------------------------------------------------------------------------------------- | -------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------- | ---------------------------------------------------------------- | | ||
| | `db.client.connection.pool.name` | string | The name of the connection pool; unique within the instrumented application. In case the connection pool implementation doesn't provide a name, instrumentation SHOULD use a combination of parameters that would make the name unique, for example, combining attributes `server.address`, `server.port`, and `db.namespace`, formatted as `server.address:server.port/db.namespace`. | | ||
| | Instrumentations that generate connection pool name following different patterns SHOULD document it. | `myDataSource` |  | | ||
| | `db.client.connection.state` | string | The state of a connection in the pool | `idle` |  | | ||
| | `db.collection.name` | string | The name of a collection (table, container) within the database. [1] | `public.users`; `customers` |  | | ||
| | `db.namespace` | string | The name of the database, fully qualified within the server address and port. [2] | `customers`; `test.users` |  | | ||
| | `db.operation.batch.size` | int | The number of queries included in a [batch operation](/docs/database/database-spans.md#batch-operations). [3] | `2`; `3`; `4` |  | | ||
| | `db.operation.name` | string | The name of the operation or command being executed. [4] | `findAndModify`; `HMSET`; `SELECT` |  | | ||
| | `db.query.parameter.<key>` | string | A query parameter used in `db.query.text`, with `<key>` being the parameter name, and the attribute value being a string representation of the parameter value. [5] | `someval`; `55` |  | | ||
| | `db.query.text` | string | The database query being executed. [6] | `SELECT * FROM wuser_table where username = ?`; `SET mykey "WuValue"` |  | | ||
| | `db.system` | string | The database management system (DBMS) product as identified by the client instrumentation. [7] | `other_sql`; `adabas`; `cache` |  | | ||
|
|
||
| **[1]:** It is RECOMMENDED to capture the value as provided by the application without attempting to do any case normalization. | ||
| If the collection name is parsed from the query text, it SHOULD be the first collection name found in the query and it SHOULD match the value provided in the query text including any schema and database name prefix. | ||
|
|
||
Oops, something went wrong.