Deprecate environment variables which do not interoperate with file config when ready for stabilization

[jack-berg]

As discussed here, we do not want to recommend multiple competing configuration stores. When file configuration is ready for stabilization, we should deprecate any environment variables which do not interoperate.

[VidhiPhatnani]

Issue: When attempting to use both the otel-profiling JAR (for trace-to-profiling linking) and the opentelemetry-samplers JAR (specified via OTEL_JAVAAGENT_EXTENSIONS env variable), the Opentelemetry Java Agent does not handle them together.

• If only otel-profiling jar is set as an environment variable, profiling and linking work correctly.
• If both the otel-profiling jar as env variable as well as opentelemetry-samplers jar as jvm arg ( -Dotel.javaagent.extensions ) are set then the trace-to-profiling linking stops working, but the SDK configuration is correctly applied.

Additionally, the sdk-config.yaml does not seem to support any other jar when provided as an environment variable.

I would really appreciate any guidance on resolving this issue. Thank you for the insights.

[jack-berg]

I'm not familiar with the otel-profiling jar - can you link to the source code for that?

Additionally, the sdk-config.yaml does not seem to support any other jar when provided as an environment variable.

Can you elaborate?