Node.JS OpenTelemetry (OTel) -
E2E Observability
Troubleshooting Node.JS-based applications can be tough if you don’t have proper observability. One rather simple way to gain observability capabilities is by implementing OpenTelemetry (OTel) OSS. OTel has become essential for Node.JS developers, enabling them to generate, collect, and export observability data (metrics, logs, and traces) in cloud-native and microservices-based architectures. Some E2E observability solutions are based on OTel and enrich it to match developers’ needs.
OTel Node.JS auto-instrumentation
We at Helios are leveraging OTel to deliver maximal value for developers working on distributed systems and microservices- We simplify the implementation, offer trace based visualization and collect granular data of the entire payload for fast troubleshooting. Our approach for OTel auto-instrumentation in Node.JS is easy to implement or maintain and doesn’t require any code changes.
No code changes
No agent required - just `npm install` the Helios OpenTelemetry SDK and add a few environment variables - no need to change anything else. Alternatively, you can install using Kubernetes operators or using AWS Lambda layer.
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 HTTP, gRPC and Kafka messages in the full context of their traces, and more.
No magic tricks
The library's source code is built on top of OpenTelemetry’s Node.JS SDK. Easily understand what’s happening, and debug if necessary.
The value of Helios for Node.JS developers
Investigate issues, reproduce scenarios, and generate tests faster with actionable data across your microservices, messaging systems, data pipelines, and databases – Minimize MTTR and dramatically improve troubleshooting efficiency.
Node.JS 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 Node.JS
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
Identify bottlenecks in app flows Instantly identify and analyze bottlenecks
Node.JS 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 SDK is built on top of OpenTelemetry’s Python SDK, and uses industry-standard instrumentation techniques.
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 best way to locate issues and identify their root cause faster than ever.
We support the same versions that are supported by OpenTelemetry, Python 3.7 or later.
Trusted by
