OpenTelemetry instrumentation still active after quarkus.otel.sdk.disabled=true

[brunobat]

Describe the bug

OpenTelemetry instrumentation is still active even when the SDK is disabled, therefore performing a non trivial amount of work and allocations that are not needed.

See the following flamegraph:

This must be corrected.

Expected behavior

When quarkus.otel.sdk.disabled=true the amount of OpenTelemetry related work must be near zero.

Actual behavior

14,23% of all samples in the above flamegraph are OpenTelemetry related.

How to Reproduce?

Using this project: https://github.com/brunobat/quarkus-observability-perf
Set quarkus.otel.sdk.disabled=true
Executing this hyperfoill test script to generate loa: https://github.com/brunobat/quarkus-observability-perf/blob/main/hyperfoil-scripts/quarkus-otel-perf.hf.yaml
And profiling the the execution with async profiler.

Data of the test execution can be seen performance test environment. Please contact me for details.

This affects all versions of the OpenTelemetry extension.

[brunobat]

quarkus.otel.sdk.disabled must be checked on each OTel related recorder.

[geoand]

Seems like something we should fix for 3.15

[quarkus-bot]

@brunobat triage/backport* labels may not be added to an issue. Please add them to the corresponding pull request.

_{This message is automatically generated by a bot.}

[brunobat]

This is the flamegraph after the merge when OTel is disabled at runtime:

Th PR seems ok.

[quarkus-bot]

@brunobat triage/backport* labels may not be added to an issue. Please add them to the corresponding pull request.

_{This message is automatically generated by a bot.}