Replies: 1 comment 9 replies
-
HI @patsonluk . I think this is a question for the opentelemetry-java-instrumentation project, since it's specifically about loading SPI implementations into a javaagent. I'm assuming that your provider works fine without the agent in place, if you're just using standard autoconfigure to build an SDK? |
Beta Was this translation helpful? Give feedback.
9 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi all,
We are trying to provide our own implementation of
ConfigurableSpanExporterProvider
, with the corresponding META-INF file to list our implementation as a service provider.However, we cannot seem to get our provider to load properly via
-Dotel.traces.exporter
The issue seems that https://github.com/open-telemetry/opentelemetry-java/blob/main/sdk-extensions/autoconfigure/src/main/java/io/opentelemetry/sdk/autoconfigure/SpanExporterConfiguration.java#L34 cannot load our provider implementation. (tested with the java auto instrumentation agent 1.0.0)
We tried:
io.opentelemetry.javaagent.bootstrap.AgentClassLoader
) cannot locate it . Probably due to the AgentClassLoader has a different lookup from regular app lookupio.opentelemetry.sdk.autoconfigure.spi.ConfigurableSpanExporterProvider
, which makes sense as the bootstrap loader probably does not knowio.opentelemetry.sdk.autoconfigure.spi.ConfigurableSpanExporterProvider
from the javaagent jar (not 100% sure, didn't dig deep into the class loading logic)We could still use
-Dotel.javaagent.experimental.exporter.jar
to make things work, but we are wondering what is the correctConfigurableSpanExporterProvider
approach here?Many thanks for your kind attention!
Beta Was this translation helpful? Give feedback.
All reactions