In this blog series, we are covering application instrumentation steps for distributed tracing with OpenTelemetry standards across multiple languages. Earlier, we covered Java Application Manual Instrumentation for Distributed Traces, Golang Application Instrumentation for Distributed Traces, and DotNet Application Instrumentation for Distributed Traces. Here we are going to cover the instrumentation for NodeJS.

Customer expectations and competitive responses to trends evolve faster than the technology your enterprise relies on. That means your ability to adapt faster than the competition and satisfy customer demands is your edge in a competitive marketplace.

We’re honored to be included in Enterprise Management Associates’ EMA Top 3 Award for Observability Platforms. This award recognizes software products that help enterprises reach their digital transformation goals by optimizing product quality, time to market, cost, and ability to innovate—all the things we’re passionate about at LogDNA.

Telemetry data – the metrics and measurement data emitted by all machines and devices from servers to robots – is exploding. Telemetry data generation is growing so fast, there are no reliable estimates of just what that growth rate looks like. Theo Schlossnagle, founder of Circonus and widely respected computer scientist, estimates that telemetry data is growing at the rate of 1×1012 every ten years. Suffice to say, that’s a lot.

To realize the full potential of APM, many customers are migrating from their existing APM 10.7 clusters to DX APM. In addition, they continue to onboard new applications for monitoring. These efforts require a series of steps, including the configuration of experience views, universes, and DX Operational Intelligence services.