How to use otel.java.disabled.resource.providers

[JDUNNIN]

Hi,

I've been trying to disable the attributes like process.command_line which comes from the ProcessResourceProvider as far as I can tell.

The documentation https://opentelemetry.io/docs/languages/java/configuration/#properties-resource has the example:

For example, to disable the OS resource provider, set -Dotel.java.disabled.resource.providers=io.opentelemetry.instrumentation.resources.OsResourceProvider.

OK, so the ProcessResourceProvider I want to turn off is in the same package, so just update the file name.

I've tried configuring this property as an environment variable and as a -D option:
otel.java.disabled.resource.providers=io.opentelemetry.instrumentation.resources.ProcessResourceProvider but the process.command_line still comes out.

Lost on what to try?

I did see this issue that suggested package names changes might get in the way? #6955

Also spotted the documentation has otel.java.enabled.resource-providers which looks like a typo perhaps?

Thanks!

[laurit]

I tried out -Dotel.java.disabled.resource.providers=io.opentelemetry.instrumentation.resources.ProcessResourceProvider and works fine for me. Please provide instructions for reproducing this.

[JDUNNIN]

Hi @laurit I have made a repo which will demonstrate the issue using a build image and jaeger for the UI. https://github.com/JDUNNIN/DisableResourceProvidersEnv the readme has instructions to follow, please let me know if any issues with this. Thank you.

[laurit]

You don't seem to be using the otel agent. Are you using manual instrumentation or spring starter in your application? Or are you getting the traces from the open telemetry support built into liberty?

[JDUNNIN]

Hi @laurit it both manual instrumentation and some auto for common libraries used - a Liberty feature mpTelemetry-2.0 provides the Open Telemetry support in the server and as a result some apps get instrumentation added automatically e.g. JAX-RS APIs deployed in .war files. Any configuration starting with otel.* or OTEL_* gets passed into the Open Telemetry SDK in this code https://github.com/OpenLiberty/open-liberty/blob/integration/dev/io.openliberty.microprofile.telemetry.2.0.internal/src/io/openliberty/microprofile/telemetry20/internal/info/OpenTelemetryInfoFactoryImpl.java#L55 like:

        OpenTelemetrySdk openTelemetry = AutoConfiguredOpenTelemetrySdk.builder()
                        .addPropertiesCustomizer(x -> openTelemetryProperties) //Overrides OpenTelemetry's property order
                        .addResourceCustomizer(resourceCustomiser)
                        .setServiceClassLoader(classLoader)
                        .disableShutdownHook()
                        .build()
                        .getOpenTelemetrySdk();

Properties like OTEL_SERVICE_NAME=TestEnv are getting configured as expected but this property in the question is not working as far as I understand it. In trace we can see that openTelemetryProperties contains all the properties I have configured as expected.

Liberty also provides us access to the same configured OpenTelemetry object to create spans manually etc, and with this again we see the same results.

[laurit]

You will have to contact IBM support or OpenLiberty community for this. Judging from https://github.com/OpenLiberty/open-liberty/blob/integration/dev/io.openliberty.microprofile.telemetry.2.0.internal/src/io/openliberty/microprofile/telemetry20/internal/info/OpenTelemetryInfoFactoryImpl.java#L66 I'd guess that they override the normal resource configuration in the otel sdk so the flags won't work. Have a look at how otel sdk configures the resource providers in https://github.com/open-telemetry/opentelemetry-java/blob/2de5a2c484868d308470ad3fea4aadf3ec59005b/sdk-extensions/autoconfigure/src/main/java/io/opentelemetry/sdk/autoconfigure/ResourceConfiguration.java#L116 to see how the flag is used.

[JDUNNIN]

Thank you @laurit that is super helpful spot on the Liberty code. I will raise it with them thank you!

[JDUNNIN]

Fixed via OpenLiberty/open-liberty#30877.