db.client.connection.pool.name
Developmentstringas of v1.44.0
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.
Examples
- myDataSource
Used by
metrics (9)
- db.client.connection.count *
- db.client.connection.create_time *
- 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.use_time *
- db.client.connection.wait_time *
* required on that signal.
History
Stability label respelled from experimental to development.
Already present at v1.30.0, the oldest release tracked here (experimental).