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
Support for oTel agent in shared library format (.so file) ? #192
Comments
That's new to me, and I'm intrigued. I thought JVM agents were only for Java applications. This probably shows my ignorance on the subject, but shouldn't you be using the Java auto-instrumentation agent? https://github.com/open-telemetry/opentelemetry-java-instrumentation |
I check it already. It works fine. With this I had to use a slightly different option: Loosely it translates to following start command(Omitted few options for simplicity):
As you would know Notice the different between the two in the Similarly, other framework support is also in alpha :io.opentelemetry.jdbc, io.opentelemetry.apache-httpclient-4.0, io.opentelemetry.spring-webmvc-3.1. Besides this, it also a popular option to use native agent based on the platform. Eg: For Cloud Foundry, this is Linux x86_64(AMD64). Vendors like Dynatrace also support it. Dynatrace, for example uses this approach to inject its Final start command:
Especially, notice the option: |
Hi,
When running the
otelcol
with Java Spring boot application on CloudFoundry (via build pack) I get a following error:The agent is passed via environment variable: JBP_CONFIG_JAVA_OPTS: 'java_opts: "-agentpath:$PWD/collector/otelcol"'
The oTel binary agent I used : x86_86(or amd64) - otelcol_0.59.0_linux_amd64.tar.gz.
For binary oTel agents, it would be nice to have .so format (eg: otelcol_0.59.0_linux_amd64.so) for use with java_opts.
The text was updated successfully, but these errors were encountered: