Open dgeyer opened 1 year ago
Hi @dgeyer,
From your use of -Dotel.javaagent.debug=true
flag, I am assuming that you are trying to auto-instrument your app.
For auto configuration with auto instrumentation, could you try using Dotel.javaagent.experimental.extensions
instead of -Dotel.javaagent.extensions
flag.
Let me know if this fixes your issue.
You can also refer to the examples in the repo -
@dgeyer did that fix your issue?
@aabmass I see some are exported but I still see some exceptions in the debug mode. I will have a more detailed look tomorrow
I see the same exceptions when I add the VM param '-Dotel.javaagent.debug=true' to the example in: Auto instrumentation with auto-configuration
and run it using the run_in_docker.sh script
The traces are being exported
The exceptions are:
These exceptions do show up in the debug logs but it looks like it is not affecting the functionality of the exporter. Auto exporter seems to be working fine.
Cause behind these exceptions still need to be determined. I will keep this bug open to track this, but it is low-priority for now.
I may be able to share some light here. These libraries try to load some native libraries and implementation classes to provide with optimized network access. AFAIK these are all dependencies of gRPC:
ChannelProvider
options are provided by libraries such as io.grpc:grpc-okhttp
for OkHttpChannelProvider and io.grpc:grpc-netty
for UdsNettyChannelProviderThe rest seems to be variations of the same pattern, trying to load Java classes to trigger plug-in behavior. For example, it seems that gRPC will use JNDI if available, by trying to load DnsContextFactory.
I am using the shaded exporter-auto:
com.google.cloud.opentelemetry.exporter-auto-0.25.2-alpha-shaded.jar
With the VM params:And the Env varibles: GOOGLE_APPLICATION_CREDENTIALS and GOOGLE_CLOUD_PROJECT.
When running the application the oTel debugging shows several
ClassNotFoundException