-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing dependencies in exporter-auto #261
Comments
Hi @dgeyer, For auto configuration with auto instrumentation, could you try using Let me know if this fixes your issue. SamplesYou 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 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:
The 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
The text was updated successfully, but these errors were encountered: