npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@elastic/opentelemetry-node

v1.17.0

Published

Elastic Distribution of OpenTelemetry Node.js (EDOT Node.js)

Readme

EDOT Node.js

The Elastic Distribution of OpenTelemetry Node.js (EDOT Node.js) is a lightweight wrapper around the OpenTelemetry SDK for Node.js that makes it easy to get started using OpenTelemetry in your Node.js applications, especially if you are using Elastic Observability as your observability solution.

# Install it
npm install --save @elastic/opentelemetry-node

# Configure it
export OTEL_EXPORTER_OTLP_ENDPOINT="...your-OTLP/collector-endpoint..."
export OTEL_EXPORTER_OTLP_HEADERS="Authorization=..."
export OTEL_SERVICE_NAME="my-app"

# Start it with your application
node --import @elastic/opentelemetry-node my-app.js

See the EDOT Node.js docs for details. Some direct links:

How does EDOT Node.js differ from the OpenTelemetry JS SDK?

EDOT Node.js is very similar to the @opentelemetry/auto-instrumentations-node package from OpenTelemetry in its usage goal: a single-dependency that provides a simple path to zero-code instrumentation of Node.js applications. In general, Elastic's goal is to contribute all SDK improvements upstream. That said, there are sometimes differences that are specific to Elastic (e.g. talking to an Elastic service for central configuration, Elastic-authored additional instrumentations). Here is a concise list of differences:

  • EDOT Node.js supports dynamic central configuration of some settings of the running SDK.
  • EDOT Node.js, being a distribution of the OpenTelemetry JS SDK, always adds the telemetry.distro.* resource attributes to identify itself.
  • EDOT Node.js enables some metrics by default that are not included by @opentelemetry/auto-instrumentations-node: a subset of metrics from @opentelemetry/instrumentation-host-metrics.
  • EDOT Node.js defaults to OTEL_EXPORTER_OTLP_METRICS_TEMPORALITY_PREFERENCE=delta, which differs from the upstream OpenTelemetry JS default of cumulative.
  • EDOT Node.js disables the "log sending" feature of Node.js logging framework instrumentations (for Pino, Bunyan, and Winston) by default. Re-enable this with the ELASTIC_OTEL_NODE_ENABLE_LOG_SENDING=true environment variable. See the ELASTIC_OTEL_NODE_ENABLE_LOG_SENDING documentation for details.
  • EDOT Node.js uses the more recent import-in-the-middle createAddHookMessageChannel feature for improved ESM support. We hope to upstream support for this.
  • Internal diagnostic logging from EDOT Node.js is in a custom JSON-log format, rather than the message-string-only format from OpenTelemetry JS. diag logging in (luggite) JSON format.
  • EDOT Node.js set OTEL_LOG_LEVEL to info by default. This differs from upstream OTel JS (e.g. when using the auto-instrumentations-node package), where OTEL_LOG_LEVEL is not set, which is equivalent to OTEL_LOG_LEVEL=none.