How to fully disable all instrumentation Opentelemetry metrics?

[Gonzalo-bia]

Hello,
I'm running Quarkus 3.28.1 with OTel Collector contrib 0.136.0 and the following OTel config:

quarkus.otel.enabled=true

quarkus.otel.logs.enabled=true
quarkus.otel.logs.level=ERROR

quarkus.otel.traces.enabled=true
quarkus.otel.metrics.enabled=true

quarkus.otel.instrument.jvm-metrics=false
quarkus.otel.instrument.http-server-metrics=false
quarkus.otel.instrument.messaging=false
quarkus.otel.instrument.rest=false
quarkus.otel.instrument.resteasy-client=false

However, I still receive JVM, Kafka, AMQP, Netty and HTTP metrics.

How can I fully disable everything but custom application metrics? do I need to disable these metrics in the collector?

[quarkus-bot[bot]]

/cc @brunobat (opentelemetry), @ebullient (metrics), @jmartisk (metrics), @radcortez (opentelemetry)

[Gonzalo-bia]

quarkus.otel.sdk.disabled seems to do the trick but it disables all metrics, including custom application ones.

But I need to selectively disable metrics individually. Is is possible to supply OTel Java SDK-specific environment vbles using Quarkus properties file?

I'd like to supply OTel Java agent properties through Quarkus.

[brunobat]

I don't fully understand... Are you using the OTel java agent or the quarkus-micrometer-opentelemetry extension?
The java agent cannot be configured through Quarkus. It's an Agent.
If you are using the extension you can try this property: quarkus.micrometer.binder-enabled-default=false. For more details, please check: https://quarkus.io/guides/telemetry-micrometer#quarkus-micrometer_quarkus-micrometer-registry-enabled-default

[Gonzalo-bia]

no Micrometer, I'm simply using quarkus-opentelemetry dependency.

I don't fully understand what the OTel java agent is or how it works. It's not included in the Quarkus implementation right? I'm probably not using it.

[Gonzalo-bia]

you're right my bad, I was using quarkus-micrometer-opentelemetry extension, not quarkus-opentelemetry.

I'm no longer getting instrumentation metrics using quarkus-opentelemetry.

No the question I guess is, can I still get instrumentation metrics using quarkus-opentelemetry, or are they all Micrometer's?

[Gonzalo-bia]

ok nevermind, I already knew this answer. Yes it can be done (controlled by quarkus.otel.instrument.xxxx properties)

[brunobat]

It depends on what you what to do and the API you like the most.
Quarkus automatic instrumentation is based on Micrometer. If you need some of them, you should use quarkus-micrometer-opentelemetry and enable only the ones you need. See the link from above for more details on other configs.

If you just want the custom configs, you can use either Micrometer and disable auto-instrumentations with quarkus.micrometer.binder-enabled-default=false or use quarkus-opentelemetry, enable metrics and use the OTel API. Please mind that OTel has automatic JVM and HTTP metrics enabled, but there are properties to disable them as well.

[Gonzalo-bia]

ok I understood thanks. We don't have any Micrometer legacy in our system, so native OTel it is.