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.
Investigate Java related errors and issues, reproduce scenarios, and generate tests faster with actionable data across your microservices, messaging systems, data pipelines, and databases.
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
No. Helios is free to use.
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.
Increase your dev velocity
with actionable telemetry data