NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
npm
npm, #4282 most downloaded on npm
OpenTelemetry SDK for Node.js
Latest stable
0.301.1
Last release 13 days ago
09 Nov 2026
Ships fairly regularly
a new release about every 3 weeks
Rarely documented
notes for 10 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
6 years old
258 releases · first in 2020
Drag across the ruler to compare, or tap a release to open it.
chore: Update local dependencies to 3.1.1 for the release of stable packages.
Assets 3 Loading
There was an error while loading. Please reload this page .
All reactions
startNodeSDK() has been deprecated , use startNodeSdk() (slight capitalization change).
feat(sdk-node)!: The experimental startNodeSdk() code path for environment-based config (i.e. when not using a config file), has full option coverage. #6999 @trentm
startNodeSdk() should now be a viable replacement for new NodeSDK() , supporting similar (but not exactly the same) options for configuring most SDK components.
startNodeSDK() has been deprecated , use startNodeSdk() (slight capitalization change).
Two resource detectors have been added to the default set for new NodeSDK() users: os and serviceinstance . This means that when not specifying OTEL_NODE_RESOURCE_DETECTORS , the SDK Resource will include os.* and service.instance.id attributes.
refactor(configuration)!: The responsibility of the configuration package has been reduced to just the parsing, validation, and TypeScript types for declarative config files. #6999 @trentm
Breaking: The configuration package no longer supports creating a synthetic ConfigurationModel from environment variables.
Breaking: The configuration package API has changed: createConfigFactory() has been replaced with `parseConfigFile().
fix(instrumentation-http): don't require('forwarded-parse') in ESM builds ( #7261 ) @avens19
fix(otlp-grpc-exporter-base): avoid an incomplete mTLS warning for root-CA-only TLS configuration ( #7235 ) @LarryHu0217
fix(sdk-node): warn and skip, instead of erroring, on an unknown resource detector name in declarative config #7252 @trentm
fix(sdk-node): use OTEL_EVENT_ATTRIBUTE_COUNT_LIMIT and OTEL_LINK_ATTRIBUTE_COUNT_LIMIT environment variables for span limits #6999 @trentm
Before this change, different environment variable names (see next point), that are not in the OTel spec were used. They will still be supported as a fallback for the spec names for a period of approximately six months.
The OTEL_SPAN_ATTRIBUTE_PER_EVENT_COUNT_LIMIT and OTEL_SPAN_ATTRIBUTE_PER_LINK_COUNT_LIMIT environment variables are deprecated . Support for them will be removed sometime after six months , to allow transition to the correct environment variables in the spec .
fix(otlp-exporter-base): pick the browser fetch mode from the document origin, so exports from an opaque-origin document (e.g. a sandboxed iframe) no longer fail with mode: 'same-origin' #7211 @MO2k4
fix: raise the minimum @opentelemetry/api peer dependency version to 1.10.0 for packages that depend on @opentelemetry/core , @opentelemetry/otlp-transformer or @opentelemetry/instrumentation , as these use API 1.10 features. ( #7258 ) @volodymyrshk @pichlermarc
Combining these packages with @opentelemetry/api 1.9.x never worked: they failed at runtime. The peer dependency now makes npm report this at install time instead.
If you see a peer dependency error after upgrading, update @opentelemetry/api to 1.10.0 or later.
trentm, MO2k4, and 5 other contributors
Assets 3 Loading
There was an error while loading. Please reload this page .
All reactions
Your coding agent can read these notes before it upgrades. Set up the MCP server →
In the OpenTelemetry Specification v1.58.0 the OpenCensus compatibility requirements were deprecated . The JavaScript OpenCensus shim package will not…
The minimum supported Node.js has been raised to >=22.15.0 . This means that support for Node.js 18 and 20 has been dropped.
The public interface has changed
for notes on migrating to 3.x / 0.300.x see the upgrade guide
Only stable versions 3.0.0 are compatible with this release
chore(shim-opencensus)!: remove the @opentelemetry/shim-opencensus package
In the OpenTelemetry Specification v1.58.0 the OpenCensus compatibility requirements were deprecated . The JavaScript OpenCensus shim package will not receive any more releases after the current 0.222.0 release ( source code for last release ).
feat(instrumentation-http)!: remove deprecated serverName field from HttpInstrumentationConfig #7081
The serverName option had no effect; stable HTTP semantic conventions do not include http.server_name . Remove it from any setConfig() or constructor call.
feat(sdk-node)!: remove deprecated NodeSDKConfiguration fields logRecordProcessor , metricReader , spanProcessor and deprecated namespace re-exports node , tracing
NodeSDKConfiguration.logRecordProcessor — use logRecordProcessors instead.
NodeSDKConfiguration.metricReader — use metricReaders instead.
NodeSDKConfiguration.spanProcessor — use spanProcessors instead.
export * as node from '@opentelemetry/sdk-node' — import directly from @opentelemetry/sdk-trace-node instead.
export * as tracing from '@opentelemetry/sdk-node' — import directly from @opentelemetry/sdk-trace-base instead.
feat(sdk-logs)!: remove deprecated SdkLogRecord type alias and LoggerProviderConfig type alias #7062
SdkLogRecord — use ReadWriteLogRecord instead.
LoggerProviderConfig — use LoggerProviderOptions instead.
feat!: migrate package builds from tsc to tsdown , emitting dual CJS/ESM output from a single dist/ directory and declaring an exports map on every package #6293 @overbalance
Importing a package by its name is unaffected in both CommonJS and ESM, as is every subpath listed in its exports map.
Deep imports into the build output no longer resolve. An exports map is an allowlist that Node.js and bundlers enforce, so specifiers such as @opentelemetry/sdk-logs/build/src/... or @opentelemetry/sdk-logs/build/esm/... now fail with ERR_PACKAGE_PATH_NOT_EXPORTED . Rewriting them to the new file layout does not help — unlisted subpaths are rejected whether or not the file exists.
The emitted files moved out of build/src (CJS), build/esm and build/esnext (ESM) into dist/ , using .cjs / .mjs extensions with matching .d.cts / .d.mts declarations.
<package>/package.json is no longer importable for the same reason. Read a package's version from your own dependency metadata, or use SDK_INFO from @opentelemetry/core for the SDK version.
The non-standard esnext entry point has been removed; tools that preferred it fall back to module (ESM) or main (CJS).
Packages that ship separate Node.js and browser implementations export them under explicit subpaths, for example @opentelemetry/sdk-logs/platform . If you depend on something that is only reachable through a deep import, please open an issue so it can be considered for the public API.
feat(sdk-node)!: remove "jaeger" propagator from @opentelemetry/sdk-node #7077
OTEL_PROPAGATORS=jaeger and { jaeger: null } in the configuration object are no longer recognised. Replace with "tracecontext" .
See the 3.x migration guide for full instructions.
fix(opentelemetry-exporter-prometheus)!: default exporter host to localhost #6599 @cjihrig
chore!: bump minimum node.js version to >=22.15.0
feat(api-logs)!: move the Logs API to @opentelemetry/api and remove the standalone @opentelemetry/api-logs package #4862 @hectorhdzg
fix(exporter-prometheus)!: stop reading Prometheus exporter host and port environment variables in the exporter constructor #6966 @LarryHu0217
chore(web-common)!: clean up and deprecate network span utils #7114
These utilities were long planned for removal. They were moved from the sdk-trace-web package and are currently only used by the (deprecated) instrumentation-fetch and instrumentation-xml-http-request packages.
Drop the skipOldSemconvContentLengthAttrs vestigial option from addSpanNetworkEvents() .
feat(sdk-node)!: drop SDK package re-exports ( api , contextBase , core , logs , metrics , resources ) #7111 @pichlermarc
api / contextBase → import from @opentelemetry/api
core → import from @opentelemetry/core
logs → import from @opentelemetry/sdk-logs
metrics → import from @opentelemetry/sdk-metrics
resources → import from @opentelemetry/resources
feat(sdk-logs): mark @opentelemetry/sdk-logs as stable #7143 @trentm
See the stable CHANGELOG for future changes to the sdk-logs package.
feat!: replace the browser field in package.json with #platform subpath imports #7141 @overbalance
Resolvers with the node condition load the Node.js build; all others load the browser build. Bundlers without imports support fail; see the migration guide.
webpack needs 5.54 or later. Parcel needs package exports enabled and cannot resolve #platform from require() .
Root type declarations describe the Node.js build.
feat(instrumentation, exporter- -otlp-http, exporter- -otlp-proto)!: remove the ./platform and ./platform/browser subpath exports; import from the package root #7141 @overbalance
feat(otlp-exporter-base)!: move OTLPExporterNodeConfigBase to @opentelemetry/otlp-exporter-base/node-http #7172 @overbalance
typesVersions maps the subpaths for moduleResolution: node .
refactor!(api-logs): remove AnyValue-related types in favor of new types in the api package #6780 @trentm
The AnyValue , LogBody , and LogAttributes types are no longer exported by the api-logs package. Instead, use the AnyValue and Attributes types from the latest @opentelemetry/api package.
This is part of supporting OTEP 4485 .
feat(instrumentation): add isEnabled() to the browser InstrumentationBase ; fetch and XHR report false when patching throws #7140 @overbalance
feat(instrumentation)!: make InstrumentationBase#_enabled protected on both platforms #7202 @overbalance
The browser base no longer tracks enable() and disable() calls. Browser subclasses set _enabled themselves; one that never sets it reports isEnabled() as false.
A browser subclass that declares its own private _enabled fails to compile; rename it or declare it protected .
fix(otlp-exporter-base): suppress tracing around the browser fetch transport's own request so a fetch instrumentation cannot create an export → span → export loop #6948 @YangJonghun
fix(instrumentation-http): set error.type on spans whose status code makes them an error #7061 @mwear
fix(exporter-prometheus): prevent duplicate metric metadata and keep metric families grouped across instrumentation scopes in Prometheus scrapes #7047 @freben
fix(configuration): preserve zero-valued limits from environment variables #7060 @DenisCDev
fix(otlp-exporter-base): release the keepalive budget once the response body drains, instead of holding up the export until it does #7070 @overbalance
fix(web-common): export getElementXPath utility
This was accidentally missed when moving utilities from sdk-trace-web to web-common.
fix(opentelemetry-browser-detector): mark the package side-effect free so bundlers can tree-shake it #7135 @overbalance
fix: resolve the ESM build through the default export condition instead of import , so a resolver that activates neither import nor require sti...
Read more
overbalance, trentm, and 8 other contributors
Assets 3 Loading
There was an error while loading. Please reload this page .
All reactions
Previous 1 2 3 4 5 … 20 21 Next
Previous Next
You can’t perform that action at this time.
Nothing published for this version
Nothing published for this version
Nothing published for this version
chore: Update local dependencies to 2.12.1 for the release of stable packages.
Assets 3 Loading
There was an error while loading. Please reload this page .
All reactions
chore(web-common)!: clean up and deprecate network span utils #7114
chore(web-common)!: clean up and deprecate network span utils #7114
These utilities were long planned for removal. They were moved from the sdk-trace-web package and are currently only used by the (deprecated) instrumentation-fetch and instrumentation-xml-http-request packages.
Drop the skipOldSemconvContentLengthAttrs vestigial option from addSpanNetworkEvents() .
Assets 3 Loading
There was an error while loading. Please reload this page .
All reactions
feat(sdk-logs): deprecate SdkLogRecord in favor of ReadWriteLogRecord #6939 @pichlermarc
fix(sdk-node)!: fail-fast on Propagator creation from config file #6930 @trentm
fix(sdk-node)!: fail-fast on MeterProvider creation from config file #6954 @trentm
fix(sdk-node)!: fail-fast on TracerProvider creation from config file #6962 @trentm
fix(sdk-node)!: fail-fast on Resource creation from config file #6989 @trentm
This also breaks some usage of startNodeSDK() for environment-based config, i.e. when not using a config file. For example with OTEL_NODE_RESOURCE_DETECTORS=all , it results in an error message and a no-op SDK. (This does not impact users of new NodeSDK() -- the currently recommended mechanism to start an SDK using this package.)
Could not create OpenTelemetry SDK from configuration, SDK will not be setup: unknown ExperimentalResourceDetector name in configuration: " container "
fix(instrumentation-http): redact sensitive query parameters on incoming (server) spans; add redactedQueryParamsServer config option @dyladan
fix(sdk-node): support headers_list when creating OTLP exporters from declarative configuration #6953 @JacksonWeber
docs(sdk-logs): mark logger configuration as experimental #6996 @LarryHu0217
docs(configuration): document the ConfigModel suffix naming convention for exported types #6612 @vedantchalke36
trentm, david-luna, and 5 other contributors
Assets 3 Loading
There was an error while loading. Please reload this page .
All reactions
Previous 1 2 3 4 5 … 19 20 Next
Previous Next
You can’t perform that action at this time.
Nothing published for this version
feat(sdk-node): emit a deprecation warning when the JaegerPropagator is selected via OTEL_PROPAGATORS or declarative config; use tracecontext instead.…
feat(sdk-logs)!: configure the force flush timeout per call #6931 @LarryHu0217
(user-facing): LoggerProviderOptions.forceFlushTimeoutMillis has been removed; pass timeoutMillis to LoggerProvider.forceFlush() instead.
feat(instrumentation-http)!: emit only stable HTTP semantic conventions. The OTEL_SEMCONV_STABILITY_OPT_IN environment variable no longer changes HTTP attribute or metric emission — old (v1.7.0) and duplicate ( http / http/dup ) semconv outputs have been removed. #6819 @maryliag
feat(instrumentation-fetch)!: emit only stable HTTP semantic conventions. The semconvStabilityOptIn instrumentation config option has been removed; old (v1.7.0) and duplicate semconv outputs are no longer emitted. #6819 @maryliag
feat(instrumentation-xml-http-request)!: emit only stable HTTP semantic conventions. The semconvStabilityOptIn instrumentation config option has been removed; old (v1.7.0) and duplicate semconv outputs are no longer emitted. #6819 @maryliag
feat(instrumentation-grpc)!: emit only stable network semantic conventions. The OTEL_SEMCONV_STABILITY_OPT_IN environment variable no longer changes attribute emission — net.peer.name and net.peer.port (old) are no longer set; only server.address and server.port (stable). #6819 @maryliag
feat(sdk-logs): allow modifying ReadWriteLogRecord properties (including hrTime, hrTimeObserved, and spanContext) in accordance with the OpenTelemetry Logs specification #6923 @Babul422
feat(sdk-node): emit a deprecation warning when the JaegerPropagator is selected via OTEL_PROPAGATORS or declarative config; use tracecontext instead. @pichlermarc
feat(instrumentation-http): set error.type to status code in metrics for error requests. #6919 @raphael-theriault-swi
maryliag, pichlermarc, and 3 other contributors
Assets 3 Loading
There was an error while loading. Please reload this page .
All reactions
The OpenCensus and OpenTracing compatibility requirements in the OpenTelemetry specification have been deprecated.
refactor(sdk-logs)!: refactor BatchLogRecordProcessor constructor signature #6817 @trentm
(user-facing): BatchLogRecordProcessor now takes a single options object with all possible properties, instead of two separate arguments. For example, before new BatchLogRecordProcessor(exporter, { maxQueueSize: 1000 }) , after new BatchLogRecordProcessor({ exporter, maxQueueSize: 1000 }) .
interface BufferConfig -> interface BatchLogRecordProcessorOptions , and now includes the exporter property
interface BatchLogRecordProcessorBrowserConfig -> interface BatchLogRecordProcessorBrowserOptions
(user-facing): SimpleLogRecordProcessor now takes a single options object with all possible properties. For example, before new SimpleLogRecordProcessor(exporter) , after new SimpleLogRecordProcessor({ exporter }) . #6836
refactor(configuration)!: change config file parsing to not add default values, nor merge *_list fields #6765 @trentm
Responsibility for handling declarative config "nullBehavior" and "defaultBehavior" belongs in the "create" handling, currently in the "sdk-node" package.
docs(shim-opencensus): Notice : The @opentracing/shim-opencensus package will be removed in SDK 3.x, planned for approximately September 2026.
The OpenCensus and OpenTracing compatibility requirements in the OpenTelemetry specification have been deprecated.
chore(sdk-node)!: Drop support for deprecated OpenCensusMetricProducer from declarative config
feat(configuration): bump config schema to v1.1.0; rename without_scope_info → scope_info_enabled and without_target_info/development → target_info_enabled/development on the Prometheus pull exporter (semantics inverted), rename with_resource_constant_labels → resource_constant_labels . Validate file_format per the configuration versioning spec: accept any minor version of major 1 (e.g. 1.0 , 1.1 ), warn when the minor version is newer than supported, and reject other major versions. #6781 @MikeGoldsmith
feat(sdk-node): wire up id_generator from declarative config #6782 @MikeGoldsmith
feat(sdk-node): wire up tracer_provider.sampler from declarative config (always_on, always_off, trace_id_ratio_based, parent_based); unrecognized variants warn and fall back to ParentBased(AlwaysOn) #6506 @MikeGoldsmith
feat(propagator-env-carrier): empty name normalization #6827 @pellared
feat(propagator-env-carrier): make EnvironmentGetter read the current process.env #6853 @pellared
fix(sdk-logs): stop Logger.emit() doing work (record construction, metrics, processor onEmit ) after the LoggerProvider has shut down #6826 @anneheartrecord
fix(sdk-node): pass all config properties (endpoint, headers, timeout, TLS, compression, temporality preference, default histogram aggregation) to OTLP metric exporters in declarative config #6814 @MikeGoldsmith
fix(sdk-logs): default BatchLogRecordProcessor scheduleDelayMillis is 1000 #6796 @trentm
fix(configuration): percent-decode keys and values in resource.attributes_list per spec #6787 @MikeGoldsmith
fix(configuration): default log_level to info in env-based config initialization for consistency with file-based config #6788 @MikeGoldsmith
fix(sdk-node): fail-fast on LoggerProvider creation with startNodeSDK() and declarative config #6785 @trentm
chore(sdk-node): migrate to use the new sdk-trace package #6828 @trentm
The node re-export of @opentelemetry/sdk-trace-node and tracing re-export of @opentelemetry/sdk-trace-base have been deprecated. (Historically the @opentelemetry/sdk-node package has re-exported from a number of core packages . It is now recommended that users directly import from those other packages.)
chore(*): migrate use of sdk-trace-base and sdk-trace-node to sdk-trace #6851 @trentm
fix(instrumentation,instrumentation-http): fix codecov coverage under-reporting by merging coverage across CJS/ESM test runs #6867 @mwear
trentm, mwear, and 3 other contributors
Assets 3 Loading
There was an error while loading. Please reload this page .
All reactions
Previous 1 2 3 4 5 … 19 20 Next
Previous Next
You can’t perform that action at this time.
fix(configuration)!: stop removing null values from parsed config object #6679 @trentm
fix(configuration)!: stop removing null values from parsed config object #6679 @trentm
It is now the responsibility of the user of a parsed declarative config object, typically just the sdk-node package, to handle null values.
fix(api-logs)!: Removed NOOP_LOGGER and NoopLogger exports from @opentelemetry/api-logs . Use createNoopLogger(): Logger instead. #6713 @dyladan
feat(api-logs)!: rename scopeAttributes to attributes in LoggerOptions #6573 @pichlermarc
fix(sdk-node)!: remove buildSamplerFromConfig export #6784 @trentm
feat(sdk-node): wire up metric producers from declarative config #6712 @MikeGoldsmith
feat(sdk-logs)!: add support for attributes in LoggerOptions #6573 @pichlermarc
fix(sdk-node): pass all config properties to log record exporters in declarative config #6708 @MikeGoldsmith
fix(sdk-node): warn and ignore zero exporter timeout in declarative config #6711 @MikeGoldsmith
fix(sdk-node): pass gRPC credentials and headers to span exporter in declarative config #6705 @MikeGoldsmith
fix(otlp-transformer): do not attempt to skip groups #6704 @pichlermarc
fix(otlp-grpc-exporter-base): recreate client after 5 consecutive DEADLINE_EXCEEDED to recover from connection dropped deadlock #6296 @afharo
fix(browser-detector): use the right semantic convention for user agent resource attribute #6729 @david-luna
fix(browser-detector): user agent resource attribute always #6754 @david-luna
fix(opentelemetry-exporter-prometheus): handle additional edge cases in metric name conversion #6727 @cjihrig
fix(sdk-logs): avoid null dereference in BatchLogRecordProcessor._flushAll when an in-flight export completes between awaits #6763 @Janealter
fix(configuration): improve environment variable substitution to handle all the cases shown in the spec #6757 @trentm
trentm, david-luna, and 7 other contributors
Assets 3 Loading
There was an error while loading. Please reload this page .
All reactions
Previous 1 2 3 4 5 … 19 20 Next
Previous Next
You can’t perform that action at this time.
feat(otlp-transformer): replace protobufjs metrics serialization with custom implementation #6625 @pichlermarc
feat(otlp-transformer): replace protobufjs metrics serialization with custom implementation #6625 @pichlermarc
feat(configuration): show all config validation errors, if there are multiple #6683 @trentm
feat(sdk-node): allow startNodeSDK() without an arg #6688 @trentm
refactor(sdk-logs): alias LoggerProviderConfig to LoggerProviderOptions #6691 @david-luna
refactor(sdk-logs): use Logger.enabled() within Logger.emit() implementation #6680 @david-luna
trentm, david-luna, and pichlermarc
Assets 3 Loading
There was an error while loading. Please reload this page .
❤️ 1 Johoseph reacted with heart emoji All reactions
1 person reacted
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
One column per quarter.