Rename `db.client.connections.*` attributes to `db.client.connection.*` (#1125)
Co-authored-by: Liudmila Molkova <limolkova@microsoft.com>
This commit is contained in:
Trask Stalnaker
GitHub
parent
3b7dd893a2
commit
de58491fa5
|
|
@ -0,0 +1,22 @@
|
|||
# Use this changelog template to create an entry for release notes.
|
||||
#
|
||||
# If your change doesn't affect end users you should instead start
|
||||
# your pull request title with [chore] or use the "Skip Changelog" label.
|
||||
|
||||
# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
|
||||
change_type: breaking
|
||||
|
||||
# The name of the area of concern in the attributes-registry, (e.g. http, cloud, db)
|
||||
component: db
|
||||
|
||||
# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
|
||||
note: Rename `db.client.connections.*` attributes to `db.client.connection.*`
|
||||
|
||||
# Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
|
||||
# The values here must be integers.
|
||||
issues: [ 1125 ]
|
||||
|
||||
# (Optional) One or more lines of additional information to render under the primary note.
|
||||
# These lines will be padded with 2 spaces and then inserted directly into the document.
|
||||
# Use pipe (|) for multiline entries.
|
||||
subtext:
|
||||
|
|
@ -17,17 +17,17 @@
|
|||
|
||||
This group defines the attributes used to describe telemetry in the context of databases.
|
||||
|
||||
| Attribute | Type | Description | Examples | Stability |
|
||||
| --------------------------------- | ------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------- | ---------------------------------------------------------------- |
|
||||
| `db.client.connections.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 `server.address` and `server.port` attributes formatted as `server.address:server.port`. | `myDataSource` |  |
|
||||
| `db.client.connections.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 | The query parameters used in `db.query.text`, with `<key>` being the parameter name, and the attribute value being 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 `server.address` and `server.port` attributes formatted as `server.address:server.port`. | `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 | The query parameters used in `db.query.text`, with `<key>` being the parameter name, and the attribute value being 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.
|
||||
|
|
@ -50,7 +50,7 @@ If a parameter has no name and instead is referenced only by index, then `<key>`
|
|||
|
||||
**[7]:** The actual DBMS may differ from the one identified by the client. For example, when using PostgreSQL client libraries to connect to a CockroachDB, the `db.system` is set to `postgresql` based on the instrumentation's best knowledge.
|
||||
|
||||
`db.client.connections.state` has the following list of well-known values. If one of them applies, then the respective value MUST be used; otherwise, a custom value MAY be used.
|
||||
`db.client.connection.state` has the following list of well-known values. If one of them applies, then the respective value MUST be used; otherwise, a custom value MAY be used.
|
||||
|
||||
| Value | Description | Stability |
|
||||
| ------ | ----------- | ---------------------------------------------------------------- |
|
||||
|
|
@ -221,10 +221,19 @@ This group defines attributes for Elasticsearch.
|
|||
|
||||
"Describes deprecated db metrics attributes."
|
||||
|
||||
| Attribute | Type | Description | Examples | Stability |
|
||||
| ----------- | ------ | ---------------------------------------------------------- | -------------- | ------------------------------------------------------------------------------------------------------------- |
|
||||
| `pool.name` | string | Deprecated, use `db.client.connections.pool.name` instead. | `myDataSource` | <br>Replaced by `db.client.connections.pool.name`. |
|
||||
| `state` | string | Deprecated, use `db.client.connections.state` instead. | `idle` | <br>Replaced by `db.client.connections.state`. |
|
||||
| Attribute | Type | Description | Examples | Stability |
|
||||
| --------------------------------- | ------ | --------------------------------------------------------- | -------------- | ------------------------------------------------------------------------------------------------------------ |
|
||||
| `db.client.connections.pool.name` | string | Deprecated, use `db.client.connection.pool.name` instead. | `myDataSource` | <br>Replaced by `db.client.connection.pool.name`. |
|
||||
| `db.client.connections.state` | string | Deprecated, use `db.client.connection.state` instead. | `idle` | <br>Replaced by `db.client.connection.state`. |
|
||||
| `pool.name` | string | Deprecated, use `db.client.connection.pool.name` instead. | `myDataSource` | <br>Replaced by `db.client.connection.pool.name`. |
|
||||
| `state` | string | Deprecated, use `db.client.connection.state` instead. | `idle` | <br>Replaced by `db.client.connection.state`. |
|
||||
|
||||
`db.client.connections.state` has the following list of well-known values. If one of them applies, then the respective value MUST be used; otherwise, a custom value MAY be used.
|
||||
|
||||
| Value | Description | Stability |
|
||||
| ------ | ----------- | ---------------------------------------------------------------- |
|
||||
| `idle` | idle |  |
|
||||
| `used` | used |  |
|
||||
|
||||
`state` has the following list of well-known values. If one of them applies, then the respective value MUST be used; otherwise, a custom value MAY be used.
|
||||
|
||||
|
|
|
|||
|
|
@ -247,10 +247,10 @@ This metric is [required][MetricRequired].
|
|||
|
||||
| Attribute | Type | Description | Examples | [Requirement Level](https://opentelemetry.io/docs/specs/semconv/general/attribute-requirement-level/) | Stability |
|
||||
|---|---|---|---|---|---|
|
||||
| [`db.client.connections.pool.name`](/docs/attributes-registry/db.md) | 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 `server.address` and `server.port` attributes formatted as `server.address:server.port`. | `myDataSource` | `Required` |  |
|
||||
| [`db.client.connections.state`](/docs/attributes-registry/db.md) | string | The state of a connection in the pool | `idle` | `Required` |  |
|
||||
| [`db.client.connection.pool.name`](/docs/attributes-registry/db.md) | 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 `server.address` and `server.port` attributes formatted as `server.address:server.port`. | `myDataSource` | `Required` |  |
|
||||
| [`db.client.connection.state`](/docs/attributes-registry/db.md) | string | The state of a connection in the pool | `idle` | `Required` |  |
|
||||
|
||||
`db.client.connections.state` has the following list of well-known values. If one of them applies, then the respective value MUST be used; otherwise, a custom value MAY be used.
|
||||
`db.client.connection.state` has the following list of well-known values. If one of them applies, then the respective value MUST be used; otherwise, a custom value MAY be used.
|
||||
|
||||
| Value | Description | Stability |
|
||||
|---|---|---|
|
||||
|
|
@ -293,7 +293,7 @@ This metric is [recommended][MetricRecommended].
|
|||
|
||||
| Attribute | Type | Description | Examples | [Requirement Level](https://opentelemetry.io/docs/specs/semconv/general/attribute-requirement-level/) | Stability |
|
||||
|---|---|---|---|---|---|
|
||||
| [`db.client.connections.pool.name`](/docs/attributes-registry/db.md) | 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 `server.address` and `server.port` attributes formatted as `server.address:server.port`. | `myDataSource` | `Required` |  |
|
||||
| [`db.client.connection.pool.name`](/docs/attributes-registry/db.md) | 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 `server.address` and `server.port` attributes formatted as `server.address:server.port`. | `myDataSource` | `Required` |  |
|
||||
|
||||
|
||||
<!-- markdownlint-restore -->
|
||||
|
|
@ -331,7 +331,7 @@ This metric is [recommended][MetricRecommended].
|
|||
|
||||
| Attribute | Type | Description | Examples | [Requirement Level](https://opentelemetry.io/docs/specs/semconv/general/attribute-requirement-level/) | Stability |
|
||||
|---|---|---|---|---|---|
|
||||
| [`db.client.connections.pool.name`](/docs/attributes-registry/db.md) | 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 `server.address` and `server.port` attributes formatted as `server.address:server.port`. | `myDataSource` | `Required` |  |
|
||||
| [`db.client.connection.pool.name`](/docs/attributes-registry/db.md) | 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 `server.address` and `server.port` attributes formatted as `server.address:server.port`. | `myDataSource` | `Required` |  |
|
||||
|
||||
|
||||
<!-- markdownlint-restore -->
|
||||
|
|
@ -369,7 +369,7 @@ This metric is [recommended][MetricRecommended].
|
|||
|
||||
| Attribute | Type | Description | Examples | [Requirement Level](https://opentelemetry.io/docs/specs/semconv/general/attribute-requirement-level/) | Stability |
|
||||
|---|---|---|---|---|---|
|
||||
| [`db.client.connections.pool.name`](/docs/attributes-registry/db.md) | 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 `server.address` and `server.port` attributes formatted as `server.address:server.port`. | `myDataSource` | `Required` |  |
|
||||
| [`db.client.connection.pool.name`](/docs/attributes-registry/db.md) | 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 `server.address` and `server.port` attributes formatted as `server.address:server.port`. | `myDataSource` | `Required` |  |
|
||||
|
||||
|
||||
<!-- markdownlint-restore -->
|
||||
|
|
@ -407,7 +407,7 @@ This metric is [recommended][MetricRecommended].
|
|||
|
||||
| Attribute | Type | Description | Examples | [Requirement Level](https://opentelemetry.io/docs/specs/semconv/general/attribute-requirement-level/) | Stability |
|
||||
|---|---|---|---|---|---|
|
||||
| [`db.client.connections.pool.name`](/docs/attributes-registry/db.md) | 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 `server.address` and `server.port` attributes formatted as `server.address:server.port`. | `myDataSource` | `Required` |  |
|
||||
| [`db.client.connection.pool.name`](/docs/attributes-registry/db.md) | 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 `server.address` and `server.port` attributes formatted as `server.address:server.port`. | `myDataSource` | `Required` |  |
|
||||
|
||||
|
||||
<!-- markdownlint-restore -->
|
||||
|
|
@ -445,7 +445,7 @@ This metric is [recommended][MetricRecommended].
|
|||
|
||||
| Attribute | Type | Description | Examples | [Requirement Level](https://opentelemetry.io/docs/specs/semconv/general/attribute-requirement-level/) | Stability |
|
||||
|---|---|---|---|---|---|
|
||||
| [`db.client.connections.pool.name`](/docs/attributes-registry/db.md) | 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 `server.address` and `server.port` attributes formatted as `server.address:server.port`. | `myDataSource` | `Required` |  |
|
||||
| [`db.client.connection.pool.name`](/docs/attributes-registry/db.md) | 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 `server.address` and `server.port` attributes formatted as `server.address:server.port`. | `myDataSource` | `Required` |  |
|
||||
|
||||
|
||||
<!-- markdownlint-restore -->
|
||||
|
|
@ -483,7 +483,7 @@ This metric is [recommended][MetricRecommended].
|
|||
|
||||
| Attribute | Type | Description | Examples | [Requirement Level](https://opentelemetry.io/docs/specs/semconv/general/attribute-requirement-level/) | Stability |
|
||||
|---|---|---|---|---|---|
|
||||
| [`db.client.connections.pool.name`](/docs/attributes-registry/db.md) | 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 `server.address` and `server.port` attributes formatted as `server.address:server.port`. | `myDataSource` | `Required` |  |
|
||||
| [`db.client.connection.pool.name`](/docs/attributes-registry/db.md) | 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 `server.address` and `server.port` attributes formatted as `server.address:server.port`. | `myDataSource` | `Required` |  |
|
||||
|
||||
|
||||
<!-- markdownlint-restore -->
|
||||
|
|
@ -521,7 +521,7 @@ This metric is [recommended][MetricRecommended].
|
|||
|
||||
| Attribute | Type | Description | Examples | [Requirement Level](https://opentelemetry.io/docs/specs/semconv/general/attribute-requirement-level/) | Stability |
|
||||
|---|---|---|---|---|---|
|
||||
| [`db.client.connections.pool.name`](/docs/attributes-registry/db.md) | 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 `server.address` and `server.port` attributes formatted as `server.address:server.port`. | `myDataSource` | `Required` |  |
|
||||
| [`db.client.connection.pool.name`](/docs/attributes-registry/db.md) | 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 `server.address` and `server.port` attributes formatted as `server.address:server.port`. | `myDataSource` | `Required` |  |
|
||||
|
||||
|
||||
<!-- markdownlint-restore -->
|
||||
|
|
@ -559,7 +559,7 @@ This metric is [recommended][MetricRecommended].
|
|||
|
||||
| Attribute | Type | Description | Examples | [Requirement Level](https://opentelemetry.io/docs/specs/semconv/general/attribute-requirement-level/) | Stability |
|
||||
|---|---|---|---|---|---|
|
||||
| [`db.client.connections.pool.name`](/docs/attributes-registry/db.md) | 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 `server.address` and `server.port` attributes formatted as `server.address:server.port`. | `myDataSource` | `Required` |  |
|
||||
| [`db.client.connection.pool.name`](/docs/attributes-registry/db.md) | 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 `server.address` and `server.port` attributes formatted as `server.address:server.port`. | `myDataSource` | `Required` |  |
|
||||
|
||||
|
||||
<!-- markdownlint-restore -->
|
||||
|
|
|
|||
|
|
@ -41,9 +41,9 @@ groups:
|
|||
instrument: updowncounter
|
||||
unit: "{connection}"
|
||||
attributes:
|
||||
- ref: db.client.connections.state
|
||||
- ref: db.client.connection.state
|
||||
requirement_level: required
|
||||
- ref: db.client.connections.pool.name
|
||||
- ref: db.client.connection.pool.name
|
||||
requirement_level: required
|
||||
|
||||
- id: metric.db.client.connection.idle.max
|
||||
|
|
@ -54,7 +54,7 @@ groups:
|
|||
instrument: updowncounter
|
||||
unit: "{connection}"
|
||||
attributes:
|
||||
- ref: db.client.connections.pool.name
|
||||
- ref: db.client.connection.pool.name
|
||||
requirement_level: required
|
||||
|
||||
- id: metric.db.client.connection.idle.min
|
||||
|
|
@ -65,7 +65,7 @@ groups:
|
|||
instrument: updowncounter
|
||||
unit: "{connection}"
|
||||
attributes:
|
||||
- ref: db.client.connections.pool.name
|
||||
- ref: db.client.connection.pool.name
|
||||
requirement_level: required
|
||||
|
||||
- id: metric.db.client.connection.max
|
||||
|
|
@ -76,7 +76,7 @@ groups:
|
|||
instrument: updowncounter
|
||||
unit: "{connection}"
|
||||
attributes:
|
||||
- ref: db.client.connections.pool.name
|
||||
- ref: db.client.connection.pool.name
|
||||
requirement_level: required
|
||||
|
||||
- id: metric.db.client.connection.pending_requests
|
||||
|
|
@ -87,7 +87,7 @@ groups:
|
|||
instrument: updowncounter
|
||||
unit: "{request}"
|
||||
attributes:
|
||||
- ref: db.client.connections.pool.name
|
||||
- ref: db.client.connection.pool.name
|
||||
requirement_level: required
|
||||
|
||||
- id: metric.db.client.connection.timeouts
|
||||
|
|
@ -98,7 +98,7 @@ groups:
|
|||
instrument: counter
|
||||
unit: "{timeout}"
|
||||
attributes:
|
||||
- ref: db.client.connections.pool.name
|
||||
- ref: db.client.connection.pool.name
|
||||
requirement_level: required
|
||||
|
||||
- id: metric.db.client.connection.create_time
|
||||
|
|
@ -109,7 +109,7 @@ groups:
|
|||
instrument: histogram
|
||||
unit: "s"
|
||||
attributes:
|
||||
- ref: db.client.connections.pool.name
|
||||
- ref: db.client.connection.pool.name
|
||||
requirement_level: required
|
||||
|
||||
- id: metric.db.client.connection.wait_time
|
||||
|
|
@ -120,7 +120,7 @@ groups:
|
|||
instrument: histogram
|
||||
unit: "s"
|
||||
attributes:
|
||||
- ref: db.client.connections.pool.name
|
||||
- ref: db.client.connection.pool.name
|
||||
requirement_level: required
|
||||
|
||||
- id: metric.db.client.connection.use_time
|
||||
|
|
@ -131,5 +131,5 @@ groups:
|
|||
instrument: histogram
|
||||
unit: "s"
|
||||
attributes:
|
||||
- ref: db.client.connections.pool.name
|
||||
- ref: db.client.connection.pool.name
|
||||
requirement_level: required
|
||||
|
|
|
|||
|
|
@ -300,7 +300,7 @@ groups:
|
|||
brief: 'Vertica'
|
||||
stability: experimental
|
||||
stability: experimental
|
||||
- id: client.connections.state
|
||||
- id: client.connection.state
|
||||
stability: experimental
|
||||
type:
|
||||
allow_custom_values: true
|
||||
|
|
@ -313,7 +313,7 @@ groups:
|
|||
stability: experimental
|
||||
brief: "The state of a connection in the pool"
|
||||
examples: ["idle"]
|
||||
- id: client.connections.pool.name
|
||||
- id: client.connection.pool.name
|
||||
type: string
|
||||
stability: experimental
|
||||
brief: >
|
||||
|
|
|
|||
|
|
@ -101,12 +101,32 @@ groups:
|
|||
- id: used
|
||||
value: 'used'
|
||||
stability: experimental
|
||||
brief: "Deprecated, use `db.client.connections.state` instead."
|
||||
deprecated: "Replaced by `db.client.connections.state`."
|
||||
brief: "Deprecated, use `db.client.connection.state` instead."
|
||||
deprecated: "Replaced by `db.client.connection.state`."
|
||||
examples: ["idle"]
|
||||
- id: pool.name
|
||||
type: string
|
||||
stability: experimental
|
||||
brief: "Deprecated, use `db.client.connections.pool.name` instead."
|
||||
deprecated: "Replaced by `db.client.connections.pool.name`."
|
||||
brief: "Deprecated, use `db.client.connection.pool.name` instead."
|
||||
deprecated: "Replaced by `db.client.connection.pool.name`."
|
||||
examples: ["myDataSource"]
|
||||
- id: db.client.connections.state
|
||||
stability: experimental
|
||||
type:
|
||||
allow_custom_values: true
|
||||
members:
|
||||
- id: idle
|
||||
value: 'idle'
|
||||
stability: experimental
|
||||
- id: used
|
||||
value: 'used'
|
||||
stability: experimental
|
||||
brief: "Deprecated, use `db.client.connection.state` instead."
|
||||
deprecated: "Replaced by `db.client.connection.state`."
|
||||
examples: ["idle"]
|
||||
- id: db.client.connections.pool.name
|
||||
type: string
|
||||
stability: experimental
|
||||
brief: "Deprecated, use `db.client.connection.pool.name` instead."
|
||||
deprecated: "Replaced by `db.client.connection.pool.name`."
|
||||
examples: ["myDataSource"]
|
||||
|
|
|
|||
|
|
@ -2,6 +2,26 @@ file_format: 1.1.0
|
|||
schema_url: https://opentelemetry.io/schemas/next
|
||||
versions:
|
||||
next:
|
||||
metrics:
|
||||
changes:
|
||||
- rename_attributes:
|
||||
attribute_map:
|
||||
db.client.connections.state: db.client.connection.state
|
||||
apply_to_metrics:
|
||||
- db.client.connection.count
|
||||
- rename_attributes:
|
||||
attribute_map:
|
||||
db.client.connections.pool.name: db.client.connection.pool.name
|
||||
apply_to_metrics:
|
||||
- db.client.connection.count
|
||||
- db.client.connection.idle.max
|
||||
- db.client.connection.idle.min
|
||||
- db.client.connection.max
|
||||
- db.client.connection.pending_requests
|
||||
- db.client.connection.timeouts
|
||||
- db.client.connection.create_time
|
||||
- db.client.connection.wait_time
|
||||
- db.client.connection.use_time
|
||||
1.26.0:
|
||||
metrics:
|
||||
changes:
|
||||
|
|
|
|||
Loading…
Reference in New Issue