Is your feature request related to a problem? Please describe.
There is no way for users to pass an OpenTelemetry instance along with configuration (ConfigProvider)
This is a challenge for open-telemetry/opentelemetry-java-instrumentation#14192
Describe the solution you'd like
(suggested by @jack-berg)
Add ExtendedOpenTelemetry as implemented in https://github.com/open-telemetry/opentelemetry-java/pull/7434/files#diff-7a910dfdb3450820ee8a73b7fee511280381d9dddabfb4d5c3dc96e5a159a174
- Introduce ExtendedOpenTelemetry interface in
opentelemetry-api-incubating , which would have accessors for any incubating providers like ConfigProvider
- Introduce corresponding ExtendedOpenTelemetrySdk in SDK
When autoconfiguring, detect if incubator is present. If so, initialize / return ExtendedOpenTelemetrySdk, setting to GlobalOpenTelemetry if available.
I think we should steal this idea from the PR. Its aligned with the "Extended" prefix pattern we use in the opentelemetry-api-incubator and makes this whole thing less awkward.
Is your feature request related to a problem? Please describe.
There is no way for users to pass an
OpenTelemetryinstance along with configuration (ConfigProvider)This is a challenge for open-telemetry/opentelemetry-java-instrumentation#14192
Describe the solution you'd like
(suggested by @jack-berg)
Add
ExtendedOpenTelemetryas implemented in https://github.com/open-telemetry/opentelemetry-java/pull/7434/files#diff-7a910dfdb3450820ee8a73b7fee511280381d9dddabfb4d5c3dc96e5a159a174opentelemetry-api-incubating, which would have accessors for any incubating providers like ConfigProviderWhen autoconfiguring, detect if incubator is present. If so, initialize / return ExtendedOpenTelemetrySdk, setting to GlobalOpenTelemetry if available.
I think we should steal this idea from the PR. Its aligned with the "Extended" prefix pattern we use in the
opentelemetry-api-incubatorand makes this whole thing less awkward.