open-telemetryOpenTelemetry Meta Packages for Node
About
This module provides a way to auto instrument any Node application to capture telemetry from a number of popular libraries and frameworks. You can export the telemetry data in a variety of formats. Exporters, samplers, and more can be configured via environment variables. The net result is the ability to gather telemetry data from a Node application without any code changes.
This module also provides a simple way to manually initialize multiple Node instrumentations for use with the OpenTelemetry SDK.
Compatible with OpenTelemetry JS API and SDK 2.0+.
Installation
npm install --save @opentelemetry/api
npm install --save @opentelemetry/auto-instrumentations-node
Usage: Auto Instrumentation
This module includes auto instrumentation for all supported instrumentations and all available data exporters. It provides a completely automatic, out-of-the-box experience. Please see the Supported Instrumentations section for more information.
Enable auto instrumentation by requiring this module using the --require flag:
node --require '@opentelemetry/auto-instrumentations-node/register' app.js
If your Node application is encapsulated in a complex run script, you can also set it via an environment variable before running Node.
env NODE_OPTIONS="--require @opentelemetry/auto-instrumentations-node/register"
The module is highly configurable using environment variables. Many aspects of the auto instrumentation's behavior can be configured for your needs, such as resource detectors, exporter choice, exporter configuration, trace context propagation headers, and much more. Instrumentation configuration is not yet supported through environment variables. Users that require instrumentation configuration must initialize OpenTelemetry programmatically.
export OTEL_TRACES_EXPORTER="otlp"
export OTEL_EXPORTER_OTLP_PROTOCOL="http/protobuf"
export OTEL_EXPORTER_OTLP_COMPRESSION="gzip"
export OTEL_EXPORTER_OTLP_TRACES_ENDPOINT="https://your-endpoint"
export OTEL_EXPORTER_OTLP_HEADERS="x-api-key=your-api-key"
export OTEL_EXPORTER_OTLP_TRACES_HEADERS="x-api-key=your-api-key"
export OTEL_RESOURCE_ATTRIBUTES="service.namespace=my-namespace"
export OTEL_NODE_RESOURCE_DETECTORS="env,host,os,serviceinstance"
export OTEL_SERVICE_NAME="client"
export NODE_OPTIONS="--require @opentelemetry/auto-instrumentations-node/register"
node app.js
By default, all SDK resource detectors are used, but you can use the environment variable OTEL_NODE_RESOURCE_DETECTORS to enable only certain detectors, or completely disable them:
envhostosprocessserviceinstancecontaineralibabaawsazuregcpall- enable all resource detectorsnone- disable resource detection
For example, to enable only the env, host detectors:
export OTEL_NODE_RESOURCE_DETECTORS="env,host"
By default, all Supported Instrumentations are enabled, unless they are annotated with "default disabled".
You can use the environment variable OTEL_NODE_ENABLED_INSTRUMENTATIONS to enable only certain instrumentations, including "default disabled" ones
OR the environment variable OTEL_NODE_DISABLED_INSTRUMENTATIONS to disable only certain instrumentations,
by providing a comma-separated list of the instrumentation package names without the @opentelemetry/instrumentation- prefix.
For example, to enable only @opentelemetry/instrumentation-http and @opentelemetry/instrumentation-nestjs-core instrumentations:
export OTEL_NODE_ENABLED_INSTRUMENTATIONS="http,nestjs-core"
To disable only @opentelemetry/instrumentation-net:
export OTEL_NODE_DISABLED_INSTRUMENTATIONS="net"
If both environment variables are set, OTEL_NODE_ENABLED_INSTRUMENTATIONS is applied first, and then OTEL_NODE_DISABLED_INSTRUMENTATIONS is applied to that list.
Therefore, if the same instrumentation is included in both lists, that instrumentation will be disabled.
To enable logging for troubleshooting, set the log level by setting the OTEL_LOG_LEVEL environment variable to one of the following:
noneerrorwarninfodebugverboseall
The default level is info.
Notes:
- In a production environment, it is recommended to set
OTEL_LOG_LEVELtoinfo. - Logs are always sent to console, no matter the environment, or debug level.
- Debug logs are extremely verbose. Enable debug logging only when needed. Debug logging negatively impacts the performance of your application.
Usage: Instrumentation Initialization
OpenTelemetry Meta Packages for Node automatically loads instrumentations for Node builtin modules and common packages.
Custom configuration for each of the instrumentations can be passed to the function, by providing an object with the name of the instrumentation as a key, and its configuration as the value.
const { NodeTracerProvider } = require('@opentelemetry/sdk-trace-node');
const { getNodeAutoInstrumentations } = require('@opentelemetry/auto-instrumentations-node');
const { CollectorTraceExporter } = require('@opentelemetry/exporter-collector');
const { resourceFromAttributes } = require('@opentelemetry/resources');
const { ATTR_SERVICE_NAME } = require('@opentelemetry/semantic-conventions');
const { SimpleSpanProcessor } = require('@opentelemetry/sdk-trace-base');
const { registerInstrumentations } = require('@opentelemetry/instrumentation');
const exporter = new CollectorTraceExporter();
const provider = new NodeTracerProvider({
resource: resourceFromAttributes({
[ATTR_SERVICE_NAME]: 'basic-service',
}),
spanProcessors: [
new SimpleSpanProcessor(exporter),
],
});
provider.register();
registerInstrumentations({
instrumentations: [
getNodeAutoInstrumentations({
// load custom configuration for http instrumentation
'@opentelemetry/instrumentation-http': {
applyCustomAttributesOnSpan: (span) => {
span.setAttribute('foo2', 'bar2');
},
},
}),
],
});
Supported instrumentations
- @opentelemetry/instrumentation-amqplib
- @opentelemetry/instrumentation-aws-lambda
- @opentelemetry/instrumentation-aws-sdk
- @opentelemetry/instrumentation-bunyan
- @opentelemetry/instrumentation-cassandra-driver
- @opentelemetry/instrumentation-connect
- @opentelemetry/instrumentation-cucumber
- @opentelemetry/instrumentation-dataloader
- @opentelemetry/instrumentation-dns
- @opentelemetry/instrumentation-express
- @opentelemetry/instrumentation-fastify (deprecated, default disabled)
- This component is deprecated in favor of the official instrumentation package
@fastify/otel, maintained by the Fastify authors.- Please see here for instructions on how to use
@fastify/otel.
- Please see here for instructions on how to use
- This component will be removed on June 30, 2025
- This component is deprecated in favor of the official instrumentation package
- @opentelemetry/instrumentation-fs (default disabled)
- @opentelemetry/instrumentation-generic-pool
- @opentelemetry/instrumentation-graphql
- @opentelemetry/instrumentation-grpc
- @opentelemetry/instrumentation-hapi
- @opentelemetry/instrumentation-http
- @opentelemetry/instrumentation-ioredis
- @opentelemetry/instrumentation-kafkajs
- @opentelemetry/instrumentation-knex
- @opentelemetry/instrumentation-koa
- @opentelemetry/instrumentation-lru-memoizer
- @opentelemetry/instrumentation-memcached
- @opentelemetry/instrumentation-mongodb
- @opentelemetry/instrumentation-mongoose
- @opentelemetry/instrumentation-mysql
- @opentelemetry/instrumentation-mysql2
- @opentelemetry/instrumentation-nestjs-core
- @opentelemetry/instrumentation-net
- @opentelemetry/instrumentation-oracledb
- @opentelemetry/instrumentation-pg
- @opentelemetry/instrumentation-pino
- @opentelemetry/instrumentation-redis
- @opentelemetry/instrumentation-restify
- @opentelemetry/instrumentation-runtime-node
- @opentelemetry/instrumentation-socket.io
- @opentelemetry/instrumentation-undici
- @opentelemetry/instrumentation-winston
Useful links
- For more information on OpenTelemetry, visit: https://opentelemetry.io/
- For more about OpenTelemetry JavaScript: https://github.com/open-telemetry/opentelemetry-js
License
APACHE 2.0 - See LICENSE for more information.