NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
npm
npm, #1365 most downloaded on npm
OpenTelemetry logs SDK
Latest stable
3.1.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 60 stable releases
Nothing withdrawn
no release was ever pulled
4 years old
67 releases · first in 2023
Drag across the ruler to compare, or tap a release to open it.
fix(resources): specify full path for ioreg command on Darwin, and kenv command on BSD for host.id @trentm
host.id @trentmfeat(resources): Deprecate envDetector in favor of separate resourceAttributesEnvDetector and serviceNameEnvDetector. Also mark serviceInstanceIdDetec…
envDetector in favor of separate resourceAttributesEnvDetector and serviceNameEnvDetector. Also mark serviceInstanceIdDetector as stable (the service.instance.id semconv attribute is now stable). #6999 @trentm@opentelemetry/api peer dependency so Yarn PnP can resolve it for context-zone-peer-dep #7268 @Vivek1898@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
@opentelemetry/api 1.9.x never worked: they failed at runtime. The peer dependency now makes npm report this at install time instead.@opentelemetry/api to 1.10.0 or later.@opentelemetry/api v1.10.0 needs SDK 3.x #7253 @adityareddy-devYour coding agent can read these notes before it upgrades. Set up the MCP server →
In the OpenTelemetry Specification v1.58.0 the OpenTracing compatibility requirements were deprecated. The JavaScript OpenTracing shim package will no…
>=22.15.0. This means that support for Node.js 18 and 20 has been dropped.0.300.0 are compatible with this release@opentelemetry/sdk-trace-node package #7054
@opentelemetry/sdk-trace package.
See the 3.x migration guide for full migration instructions.@opentelemetry/shim-opentracing package
AsyncHooksContextManager #7078tsc to tsdown, emitting dual CJS/ESM output from a single dist/ directory and declaring an exports map on every package #6293 @overbalance
exports map.exports map is an allowlist that Node.js and bundlers enforce, so specifiers such as @opentelemetry/core/build/src/... or @opentelemetry/core/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.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.esnext entry point has been removed; tools that preferred it fall back to module (ESM) or main (CJS).@opentelemetry/core/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.getTimeOrigin, otperformance, _globalThis, and unrefTimer from @opentelemetry/core #7053
getTimeOrigin() — use performance.timeOrigin directly.otperformance — use the global performance object directly._globalThis — use globalThis directly.unrefTimer(timer) — call timer.unref() directly in your own code.TracerProviderOptions.forceFlushTimeoutMillis #7057
timeoutMillis to provider.forceFlush({ timeoutMillis }) instead. The default timeout is 30000ms.@opentelemetry/propagator-jaeger package #7077
W3CTraceContextPropagator. Use W3CTraceContextPropagator from @opentelemetry/core instead.@opentelemetry/exporter-jaeger package
@opentelemetry/sdk-trace-base and @opentelemetry/sdk-trace-web packages #7117
@opentelemetry/sdk-trace package.
See the 3.x migration guide for full migration instructions.browser field in package.json with #platform subpath imports #7141 @overbalance
node condition load the Node.js build; all others load the browser build. Bundlers without imports support fail; see the migration guide.#platform from require()../detectors/platform and ./detectors/platform/browser subpath exports; import from the package root #7141 @overbalance./platform and ./platform/browser subpath exports; import from the package root #7141 @overbalanceLoggerConfig.disabled with enabled to match the specification #7160
disabled: true with enabled: false, and disabled: false with enabled: true. Loggers remain enabled by default.maxExportBatchSize option in PeriodicExportingMetricReader@opentelemetry/sdk-logs as stable #7143 @trentmdisableAutoFlushOnDocumentHide to BatchSpanProcessorOptions and BatchLogRecordProcessorOptions, deprecate BatchSpanProcessorBrowserOptions and BatchLogRecordProcessorBrowserOptions #7140 @overbalancedefault export condition instead of import, so a resolver that activates neither import nor require still finds an entry point #7132 @overbalanceRandomIdGenerator id generators prototype methods, so subclasses can override them #7190 @overbalancestartSpan toward attributeCountLimit #7176 @overbalanceglobalThis.process in the browser build #7173 @overbalancefalse instead of undefined from the browser getBooleanFromEnv #7188 @overbalanceundefined properties #7207 @trentm
isAnyValue() now returns true for {aStr: 'bob', anUndefined: undefined}. This restores the behavior of the old isLogAttributeValue from version 2.x of the sdk-logs package.cleanAttributes() and maybeAddAttribute(), will now drop undefined properties from objects. For example, logger.emit(attributes: {myAttr: {aStr: 'bob', anUndefined: undefined}, ...) will include attributes: {myAttr: {aStr: 'bob'}}.@opentelemetry/sdk-trace-web package from examples and bundler tests #7095StackContextManager in @opentelemetry/sdk-trace package #7086main, so a maintenance release no longer overwrites it.devEngines #7093 @overbalance
^24.11.1 || >=26.0.0 with npm >=11.10.0; both are advisory and warn rather than fail. The published packages are unaffected and still support Node.js >=22.15.0, which the test matrix continues to cover.module field from package.json; bundlers resolve the ESM build through the exports map #7130 @overbalancepack --json output, which is keyed by package name instead of an array #7133 @overbalanceprocess shim from the repo root, so browser tests run with isolated installs #7137 @overbalanceversion target defaults by the target name, so a cache hit restores the generated src/version.ts #7134 @overbalancetest, test:browser and test:webworker targets compile their dependencies first, since tests load dependencies from their dist #7139 @overbalancenode_modules, so workspace dependencies resolve and entry points load fully instead of being skipped #7138 @overbalancenpm run lint #7200 @overbalance@opentelemetry/resources to devDependencies, since only tests use it #7200 @overbalancepagehide listener from the browser BatchSpanProcessor, it was registered on document and never ran, and visibilitychange already flushes on unload #7153 @adityareddy-devpagehide listener from the browser BatchLogRecordProcessor, it was registered on document and never ran, and visibilitychange already flushes on unload #7153 @adityareddy-devReturnType<typeof setTimeout> instead of NodeJS.Timeout #7174 @overbalance…and BatchLogRecordProcessorOptions, deprecate BatchSpanProcessorBrowserOptions and BatchLogRecordProcessorBrowserOptions #7140 @overbalance
browser field in package.json with #platform subpath imports #7141 @overbalance
node condition load the Node.js build; all others load the browser build. Bundlers without imports support fail; see the migration guide.#platform from require()../detectors/platform and ./detectors/platform/browser subpath exports; import from the package root #7141 @overbalance./platform and ./platform/browser subpath exports; import from the package root #7141 @overbalanceLoggerConfig.disabled with enabled to match the specification #7160
disabled: true with enabled: false, and disabled: false with enabled: true. Loggers remain enabled by default.@opentelemetry/sdk-logs as stable #7143 @trentmdisableAutoFlushOnDocumentHide to BatchSpanProcessorOptions and BatchLogRecordProcessorOptions, deprecate BatchSpanProcessorBrowserOptions and BatchLogRecordProcessorBrowserOptions #7140 @overbalanceRandomIdGenerator id generators prototype methods, so subclasses can override them #7190 @overbalancestartSpan toward attributeCountLimit #7176 @overbalanceglobalThis.process in the browser build #7173 @overbalancefalse instead of undefined from the browser getBooleanFromEnv #7188 @overbalancepagehide listener from the browser BatchSpanProcessor, it was registered on document and never ran, and visibilitychange already flushes on unload #7153 @adityareddy-devpagehide listener from the browser BatchLogRecordProcessor, it was registered on document and never ran, and visibilitychange already flushes on unload #7153 @adityareddy-devReturnType<typeof setTimeout> instead of NodeJS.Timeout #7174 @overbalanceNothing 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
Previous 1 2 3 4 5 … 19 20 Next
Previous Next
You can’t perform that action at this time.
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.