AutoConfiguredOpenTelemetrySdk found on classpath but automatic configuration is disabled

[manikmagar]

After the upgrade of OTEL to 1.29.0 #101, applications show the following warning message (see #106 ) -

11:19:48.030 [BatchSpanProcessor_WorkerThread-1] INFO io.opentelemetry.api.GlobalOpenTelemetry correlationId= trace_id= span_id= trace_flags= - AutoConfiguredOpenTelemetrySdk found on classpath but automatic configuration is disabled. To enable, run your JVM with -Dotel.java.global-autoconfigure.enabled=true

This behavior is caused due to PR open-telemetry/opentelemetry-java#5010 which changed to auto-SDK configuration to opt-in and this PR open-telemetry/opentelemetry-java#5564 changed to setResultAsGlobal from true to false.

For mule-opentelemetry-module, we are manually initializing the SDK and hence should not need that JVM opt-in but then a change in the behavior of setResultAsGlobal resulted in OTEL SDK self-instrumentation code not getting a valid instance of OpenTelemetry.

A similar problem is reported here open-telemetry/opentelemetry-java#5862.

For this module, we should explicitly set the result as global until SDK provides some way (eg open-telemetry/opentelemetry-java#5021 ).