-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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 Splunk OpenTelemetry Java Instrumentation #825
Comments
Hey there @mateuszrzeszutek. We would be happy to accept such a contribution, although unlike YourKit it should be enabled via a service binding which contains connection information such as the destination to stream data to. Most of the other agents behave like this, but YourKit and a small number of others are manually enabled because they accept inbound connections (no obvious connection information) instead of making outbound connections. |
@mateuszrzeszutek are there any updates on this support? |
Hey @metacubed, |
Just an update -- we are come back around on this and hope to contribute a service binding in the near future. Thanks for your patience. |
This framework will wire up the splunk distribution of opentelemetry java for auto-instrumentation and direct ingest. It leverages VCAP_SERVICES and the existence of a service binding with a specific name (splunk-o11y). Signed-off-by: Jason Plumb [email protected] Resolves issue cloudfoundry#825
Just wanted to gently nudge this in hopes of getting some eyes on #968. Thanks. |
Hi,
I want to add a new framework that adds Splunk OTel instrumentation agent support. The agent collects telemetry sends it usually to either OpenTelemetry collector or the SignalFX Smart Agent.
The new framework will only be added when it's explicitly
enabled
(similar to how it's done in e.g. YourKit profiler). It'll download a jar with the Java agent and pass its path to the JVM through-javaagent
together with some system properties (in case the user wants to change the default configuration of the agent).Please let me know if it's OK to add this here -- I assumed that this repo would be a good place because there already are some Java agents here (AppD, NewRelic etc).
The text was updated successfully, but these errors were encountered: