Java observability-  
OpenTelemetry (OTel) Instrumentation

Troubleshooting Java-based microservices can be tough if you don’t have proper observability based on instrumenting your code. One rather simple way to gain observability is by OpenTelemetry (OTel). OTel has become an essential OSS tool for Java developers, enabling them (with the help of 3rd party tools) to generate, collect, export and visualize telemetry data (metrics, logs, and traces) in cloud-native and microservices-based architectures.

OTel auto-instrumentation in Java

Helios is leveraging OTel to deliver more value for developers working on distributed systems and microservices. Our approach for OTel auto-instrumentation in Java is easy to implement and maintain and doesn’t require any code changes. 

No code changes

No agent required - just add Helios OpenTelemetry JAR and add a few environment variables - no need to change anything else.

Get all the context you need

Visualize complex sync and async flows, get a dynamic catalog of your APIs based on real traffic, get visibility into Kafka messages in the full context of their traces, and more. ​

No magic tricks

The library's source code is based on OpenTelemetry’s code which is open to all. Easily understand what’s happening, and debug if necessary.

The value for Java developers 

Investigate Java related errors and issues, reproduce scenarios, and generate tests faster with actionable data across your microservices, messaging systems, data pipelines, and databases.

Java Observability 

Visibility – See your service map and API catalog easily

Interactions’ Payloads – Gain visibility into the communication between various components and inspect payloads

Onboarding – Allows new developers and SREs to easily understand your architecture

Troubleshooting in Java

Root Cause Analysis – Quickly pinpoint the root cause of your issues using Stack trace, error logs, and trace correlation

Replay Flows – Find failed requests, generate snippets, and re-run them with the same or different parameters

Java Testing

Pinpoint Failed Tests – Efficiently pinpoint the root cause of failed tests and gain insight into tests running in CI/CD

Trace-based Testing – Eliminate the need to build testing infrastructure by creating trace-based tests from real traffic

Autogenerate Tests – From traces to improve validation

Collaboration

Share – Traces, tests and triggers with your team

Collaborate – Generate, test, build and edit tests together

Visibility – Give your team visibility of issues in your local environment

FAQs

Detailed instructions can be found in our docs.
Completely. The Helios OpenTelemetry agent jar uses industry-standard instrumentation techniques that are part of the JVM ecosystem.

No. Helios is free to use. 

Our instrumentation is configured to collect all the data you may need to troubleshoot your application and to make sure that context is propagated properly across different services and provides the bests way to locate issues and identify their root cause faster than ever.
We support the same versions that are supported by OpenTelemetry, Java 8.
We provide several methods of making sure your sensitive data remains confidential. You may collect metadata only (with no payloads at all) or obfuscate your payloads. If you need any more capabilities, feel free to reach out.

Helios’ approach to OTel Instrumentation in Java

A mechanism that involves creating proxy libraries and leveraging the AST manipulation approach to replace the imports during or before compilation. We explain why we took this approach in this blog post.  

Trusted by

Increase your dev velocity
with actionable telemetry data