@elastic/opentelemetry-node 1.1.0
Changelog
-
BREAKING CHANGE: This includes an update to
@opentelemetry/instrumentation-aws-sdk
v0.54.0 which inclues the following breaking changes:- Instrumentation of AWS SDK v2 has been dropped. See https://github.com/open-telemetry/opentelemetry-js-contrib/blob/main/plugins/node/opentelemetry-instrumentation-aws-sdk/CHANGELOG.md#0510-2025-04-08. (#788)
- The
aws.regionspan attribute has been changed tocloud.region. See https://github.com/open-telemetry/opentelemetry-js-contrib/blob/main/plugins/node/opentelemetry-instrumentation-aws-sdk/CHANGELOG.md#0540-2025-06-02. (#814)
-
feat: Add env var
ELASTIC_OTEL_HOST_METRICS_DISABLEDto control whether
EDOT Node.js will collect host metrics (process.*). This
means users can disable host metrics without affecting metrics from instrumentations.
(#736) -
The
ELASTIC_OTEL_METRICS_DISABLEDenvironment variable is now deprecated.
UseOTEL_METRICS_EXPORTER=none(instead ofELASTIC_OTEL_METRICS_DISABLED=true)
to disable any metrics being exported by EDOT Node.js. -
feat: Restore the
@elastic/opentelemetry-node/sdkentry-point and show how
to use it to bootstrap the EDOT Node.js SDK in code. This means using
node --import ./telemetry.mjs app.js, rather than the typical zero-code
node --import @elastic/opentelemetry-node app.jsmethod for starting the SDK.
(#718)The
./telemetry.mjsfile uses APIs exported by@elastic/opentelemetry-node/sdk
to configure and start the OpenTelemetry Node.js SDK. See
examples/telemetry.mjs.WARNING: Bootstrapping the Node SDK in code often means using
OpenTelemetry JS APIs that are not yet stable. These APIs may break in
minor versions of@elastic/opentelemetry-node. -
chore: add custom GCP resource detector to avoid internal telemetry to be sent. See open-telemetry/opentelemetry-js-contrib#2320.
(#709)