Unable to collect db.client.operation.duration

[mfridljand]

Hello,
I have a (test) application on Hikari DB (com.zaxxer.hikari.HikariDataSource). With 2.25 agent multiple “db.client.connections” metrics are collected

• db.client.connections.use_time
• db.client.connections.wait_time
• db.client.connections.pending_requests
• db.client.connections.create_time
• db.client.connections.max
• db.client.connections.usage
• db.client.connections.idle.min

However, the “db.client.operation.duration” metric does not show up.

Instrumentation: io.opentelemetry.jdbc:2.25.0-alpha
An except from the agent’s log file:

[otel.javaagent 2026-03-09 09:37:44:086 +0000] [scheduling-1] 
  INFO io.opentelemetry.exporter.logging.LoggingSpanExporter - 'HikariDataSource.getConnection' : 
    0035ae68b99be2119ff5deb3406c0255 81b8a66be6ac0b1b INTERNAL [tracer: io.opentelemetry.jdbc:2.25.0-alpha] 
	    AttributesMap{data={db.name=testdb, thread.name=scheduling-1, db.user=sa, code.namespace=com.zaxxer.hikari.HikariDataSource, db.connection_string=h2:mem:, db.system=h2, code.function=getConnection, thread.id=159}, 
		capacity=128, totalAddedValues=8}
[otel.javaagent 2026-03-09 09:37:44:086 +0000] [scheduling-1] 
INFO io.opentelemetry.exporter.logging.LoggingSpanExporter - 'SELECT testdb.metrics_data' : 
   0035ae68b99be2119ff5deb3406c0255 571cbd3f8a148fd3 CLIENT [tracer: io.opentelemetry.jdbc:2.25.0-alpha] 
      AttributesMap{data={db.sql.table=metrics_data, db.operation=SELECT, db.name=testdb, thread.name=scheduling-1, db.user=sa, db.connection_string=h2:mem:, db.system=h2, thread.id=159, db.statement=SELECT DISTINCT metric_service FROM metrics_data}
		 , capacity=128, totalAddedValues=9}

My configuration is quite usual. I tested with

otel.instrumentation.jdbc.experimental.capture-query-parameters=false
as well as with
otel.instrumentation.jdbc.experimental.capture-query-parameters=false
otel.instrumentation.jdbc-datasource.enabled=true
otel.semconv-stability.opt-in=database

The agent log is attached.
otel_agent_sda_260309.log

Thanks,
Regards, Mihail

[laurit]

otel.semconv-stability.opt-in=database is needed to enable collection of db.client.operation.duration metric

[mfridljand]

Thanks,
this is one of the attempted configuration options.
otel.semconv-stability.opt-in=database
It is enabled on two systems, but it does not seem to have any effect, unfortunately. Does the log file provide anything useful?

For example, the jdbc as well as hibernate tracers seem to be active.

[otel.javaagent 2026-03-10 09:37:26:812 +0100] [qtp1253241180-71] INFO io.opentelemetry.exporter.logging.LoggingSpanExporter - 'Transaction.commit' : 4cb27ba61bac98580273d9c7a49c35cf 402a6f7e0c535593 
		INTERNAL [tracer: io.opentelemetry.hibernate-6.0:2.25.0-alpha] AttributesMap{data={thread.id=71, thread.name=qtp1253241180-71}, capacity=128, totalAddedValues=2}

[otel.javaagent 2026-03-10 09:37:26:812 +0100] [qtp1253241180-71] INFO io.opentelemetry.exporter.logging.LoggingSpanExporter - 'SELECT testdb.metrics_data' : 4cb27ba61bac98580273d9c7a49c35cf e040a25d1d22c83f CLIENT [tracer: io.opentelemetry.jdbc:2.25.0-alpha] 
	AttributesMap{data={db.sql.table=metrics_data, db.operation=SELECT, thread.id=71, thread.name=qtp1253241180-71, db.name=testdb, db.connection_string=h2:mem:, db.user=sa, db.statement= SELECT COUNT(*) FROM metrics_data WHERE metric_service = ? , db.system=h2}, capacity=128, totalAddedValues=9}
[otel.javaagent 2026-03-10 09:37:26:813 +0100] [qtp1253241180-71] INFO io.opentelemetry.exporter.logging.LoggingSpanExporter - 'DELETE testdb.metrics_data' : 4cb27ba61bac98580273d9c7a49c35cf 2aa08d859691a5e6 CLIENT [tracer: io.opentelemetry.jdbc:2.25.0-alpha] 
	AttributesMap{data={db.sql.table=metrics_data, db.operation=DELETE, thread.id=71, thread.name=qtp1253241180-71, db.name=testdb, db.connection_string=h2:mem:, db.user=sa, db.statement= DELETE FROM metrics_data md WHERE md.metric_service = ? AND EXISTS ( SELECT ? FROM metrics_data newer WHERE newer.metric_service = md.metric_service AND newer.metric_name = md.metric_name AND newer.time_stamp > md.time_stamp ) , db.system=h2}, capacity=128, totalAddedValues=9}

But still no db.client.operation.duration metric available yet.

How is it possible to detect what is going on in the log?

Regards,
Mihail

[laurit]

Does the log file provide anything useful?

As far as I know it doesn't.

You should see db.collection.name instead of db.sql.table when otel.semconv-stability.opt-in=database is set. From that I presume that wherever you set it doesn't take effect. Usually you either add -Dotel.semconv-stability.opt-in=database to jvm arguments or set OTEL_SEMCONV_STABILITY_OPT_IN environment variable.

[mfridljand]

External configuration file via -Dotel.javaagent.configuration-file is used. The configuration contains value for quite different settings like

• otel.javaagent.debug
• otel.exporter.otlp.endpoint
• otel.resource.attributes
• otel.service.name
• otel.javaagent.exclude-classes
• otel.instrumentation

I have developed own instrumentation for some of our proprietary frameworks, and by now it is quite mature environment. Everything worked as expected so far. The data is sent according to the otel.exporter.otlp.endpoint setting (there are several). The resource attributes and the service name are set. The required instrumentation is enabled/disabled correspondingly.

Like when I set now
otel.javaagent.debug = true/false
and restart the system, the agent log file starts new and has appropriate messages (either DEBUG or INFO only).

I’d not know why everything works but the
otel.semconv-stability.opt-in=database

Where db.collection.name should be visible instead of db.sql.table? db.client.connections attributes are like
"attributes": "{pool.name='HikariPool-1', state='used'}"

I will try to check whether the db.operation metric is there but simply does not show up in any used UIs.

Thanks,
Regards, Mihail

[laurit]

Where db.collection.name should be visible instead of db.sql.table? db.client.connections attributes are like
"attributes": "{pool.name='HikariPool-1', state='used'}"

in attributes of

[otel.javaagent 2026-03-10 09:37:26:812 +0100] [qtp1253241180-71] INFO io.opentelemetry.exporter.logging.LoggingSpanExporter - 'SELECT testdb.metrics_data' : 4cb27ba61bac98580273d9c7a49c35cf e040a25d1d22c83f CLIENT [tracer: io.opentelemetry.jdbc:2.25.0-alpha]
AttributesMap{data={db.sql.table=metrics_data, db.operation=SELECT, thread.id=71, thread.name=qtp1253241180-71, db.name=testdb, db.connection_string=h2:mem:, db.user=sa, db.statement= SELECT COUNT(*) FROM metrics_data WHERE metric_service = ? , db.system=h2}, capacity=128, totalAddedValues=9}

I’d not know why everything works but the
otel.semconv-stability.opt-in=database

Looking at

opentelemetry-java-instrumentation/instrumentation-api/src/main/java/io/opentelemetry/instrumentation/api/internal/SemconvStability.java

Lines 46 to 49 in 3a1dd29

	String value = System.getProperty("otel.semconv-stability.opt-in");
	if (value == null) {
	value = System.getenv("OTEL_SEMCONV_STABILITY_OPT_IN");
	}

I get the impression that unfortunately this flag currently has to be specified as a system property or an environment variable.