Java observability
with OpenTelemetry (OTel)
OTel auto-instrumentation in Java
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 of Helios for Java developers
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
No. Helios is free to use.
Helios’ approach to OTel Instrumentation in Go
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
Helios is compliant with:
