The database connection pool tag value is inconsistent with the document description.

[ixiaoyi93]

Describe the bug

The value corresponding to the tag pool name is inconsistent with the docs.

Steps to reproduce

You can find it when the service is started.

Expected behavior

As shown in the documentation, the database pool name consists of server.address, server.port, and db.namespace, for example: server.address:server.port/db.namespace.

Actual behavior

The data I queried from prometheus is as follows：

Javaagent or library instrumentation version

v2.12.0, OpenTelemetry SDK 1.46.0.

Environment

JDK: Oracle JDK 1.8.0_341-b10；
OS: Centos 7.9

Additional context

No response

[trask]

As shown in the documentation, the database pool name consists of server.address, server.port, and db.namespace, for example: server.address:server.port/db.namespace.

I haven't checked the database pool instrumentation, but sometimes it's not possible (or very difficult) to capture some of this data automatically, in which case you may need to instrument those portions manually if you need them.

If you have a chance to look at the database pool instrumentation and send PR to capture those attributes that would be great!

[onurkybsi]

I checked the code, it seems the value is set using the datasource name built by the library so not sure if the spec covers this case.

In case the connection pool implementation doesn't provide a name, instrumentation SHOULD use ...

To me, connection pool implementation does provide a name so it's fine use it and nothing needed to be changed here. cc @trask