Bump @opentelemetry/core, @opentelemetry/sdk-logs and applicationinsights in /test/performanceTests

[dependabot]

Bumps @opentelemetry/core to 2.10.0 and updates ancestor dependencies @opentelemetry/core, @opentelemetry/sdk-logs and applicationinsights. These dependencies need to be updated together.

Updates @opentelemetry/core from 2.1.0 to 2.10.0

Release notes

Sourced from @​opentelemetry/core's releases.

v2.10.0

2.10.0

🚀 Features

• feat(sdk-logs): implement log processor metrics #6554 @​anuraaga
• feat(otlp-exporter): implement exporter metrics #6480 @​anuraaga
• feat(propagator-jaeger): Notice: The @opentelemetry/propagator-jaeger package will be removed in SDK 3.x, planned for approximately September 2026. @​pichlermarc
  • The Jaeger propagator has been deprecated by the OpenTelemetry specification in favor of W3CTraceContextPropagator. This package will be removed in a future release.

🐛 Bug Fixes

• fix(sdk-trace): reject SimpleSpanProcessor.forceFlush() when a pending export fails #6771 @​LarryHu0217
• fix(sdk-trace): include trace IDs at the ratio 1 upper bound in TraceIdRatioBasedSampler #6890 @​LarryHu0217

🏠 Internal

• chore: build on Node 26 in CI #6887 @​overbalance
• chore: bump to typescript@5.2.2 @​pichlermarc

v2.9.0

2.9.0

💥 Breaking Changes

• docs(shim-opentracing): Notice: The @opentelemetry/shim-opentracing 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.

🚀 Features

• feat(sdk-metrics): add maxExportBatchSize option to PeriodicExportingMetricReader #6655 @​psx95
  • Optimized PeriodicExportingMetricReader.forceFlush to prevent redundant concurrent export cycles. Concurrent calls to forceFlush will now await any ongoing export and reuse a fresh export cycle if one is started concurrently by another caller. This ensures the latest metrics are always exported efficiently without triggering duplicate collection and export cycles.
• feat(sdk-trace): implement span processor metrics #6504 @​anuraaga
• feat(sdk-trace): add a new "sdk-trace" package to hold the Trace SDK, without environment variable configuration handling that belongs elsewhere #6775 @​trentm
  • "sdk-trace" will eventually replace all of "sdk-trace-base", "sdk-trace-node", and "sdk-trace-web".
  • The BatchSpanProcessor constructor call signature has changed in "sdk-trace". For example, before new BatchSpanProcessor(exporter, { maxQueueSize: 1000 }), after new BatchSpanProcessor({ exporter, maxQueueSize: 1000 }). #6817
  • The SimpleSpanProcessor constructor call signature has changed in "sdk-trace". For example, before new SimpleSpanProcessor(exporter), after new SimpleSpanProcessor({ exporter, selfObsMeterProvider: ... }). #6504
• feat(sdk-trace): add AlwaysRecordSampler #6188 @​majanjua-amzn

🐛 Bug Fixes

• fix(propagator-jaeger): do not throw on malformed percent-encoded uber-trace-id / uberctx-* headers during extract @​pichlermarc

🏠 Internal

• perf(sdk-metrics): defer allocation of HrTime to accumulation creation #6839 @​legendecas
• chore(*): migrate use of sdk-trace-base and sdk-trace-node to sdk-trace #6851 @​trentm
• perf(sdk-metrics): optionally capture active context for sync instruments #6848 @​legendecas

... (truncated)

Changelog

Sourced from @​opentelemetry/core's changelog.

2.10.0

🚀 Features

• feat(sdk-logs): implement log processor metrics #6554 @​anuraaga
• feat(otlp-exporter): implement exporter metrics #6480 @​anuraaga
• feat(propagator-jaeger): Notice: The @opentelemetry/propagator-jaeger package will be removed in SDK 3.x, planned for approximately September 2026. @​pichlermarc
  • The Jaeger propagator has been deprecated by the OpenTelemetry specification in favor of W3CTraceContextPropagator. This package will be removed in a future release.

🐛 Bug Fixes

• fix(sdk-trace): reject SimpleSpanProcessor.forceFlush() when a pending export fails #6771 @​LarryHu0217
• fix(sdk-trace): include trace IDs at the ratio 1 upper bound in TraceIdRatioBasedSampler #6890 @​LarryHu0217

🏠 Internal

• chore: build on Node 26 in CI #6887 @​overbalance
• chore: bump to typescript@5.2.2 @​pichlermarc

2.9.0

💥 Breaking Changes

• docs(shim-opentracing): Notice: The @opentelemetry/shim-opentracing 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.

🚀 Features

• feat(sdk-metrics): add maxExportBatchSize option to PeriodicExportingMetricReader #6655 @​psx95
  • Optimized PeriodicExportingMetricReader.forceFlush to prevent redundant concurrent export cycles. Concurrent calls to forceFlush will now await any ongoing export and reuse a fresh export cycle if one is started concurrently by another caller. This ensures the latest metrics are always exported efficiently without triggering duplicate collection and export cycles.
• feat(sdk-trace): implement span processor metrics #6504 @​anuraaga
• feat(sdk-trace): add a new "sdk-trace" package to hold the Trace SDK, without environment variable configuration handling that belongs elsewhere #6775 @​trentm
  • "sdk-trace" will eventually replace all of "sdk-trace-base", "sdk-trace-node", and "sdk-trace-web".
  • The BatchSpanProcessor constructor call signature has changed in "sdk-trace". For example, before new BatchSpanProcessor(exporter, { maxQueueSize: 1000 }), after new BatchSpanProcessor({ exporter, maxQueueSize: 1000 }). #6817
  • The SimpleSpanProcessor constructor call signature has changed in "sdk-trace". For example, before new SimpleSpanProcessor(exporter), after new SimpleSpanProcessor({ exporter, selfObsMeterProvider: ... }). #6504
• feat(sdk-trace): add AlwaysRecordSampler #6188 @​majanjua-amzn

🐛 Bug Fixes

• fix(propagator-jaeger): do not throw on malformed percent-encoded uber-trace-id / uberctx-* headers during extract @​pichlermarc

🏠 Internal

• perf(sdk-metrics): defer allocation of HrTime to accumulation creation #6839 @​legendecas
• chore(*): migrate use of sdk-trace-base and sdk-trace-node to sdk-trace #6851 @​trentm
• perf(sdk-metrics): optionally capture active context for sync instruments #6848 @​legendecas

2.8.0

🚀 Features

... (truncated)

Commits

• 76fa6b5 chore: prepare next release (#6942)
• 3787896 chore(deps): update dependency webpack-cli to v7.2.1 (#6934)
• be5f757 fix(deps): update dependency body-parser to v2.3.0 [security] (#6941)
• f6d8fbe chore(deps): lock file maintenance (#6559)
• 9612732 chore: remove examples/dice from workspaces (#6937)
• 7107906 chore: start using min-release-age in .npmrc, disable minimumReleaseAge for r...
• a7e5d11 chore(deps): update dependency webpack to v5.108.4 (#6933)
• af7a82d chore(deps): update dependency msw to v2.15.0 (#6831)
• b9f57c6 chore(deps): update dependency @​types/webpack-env to v1.18.8 (#6877)
• cbb4abf chore(deps): update ubuntu docker tag to v26 (#6635)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for @​opentelemetry/core since your current version.

Updates @opentelemetry/sdk-logs from 0.217.0 to 0.221.0

Release notes

Sourced from @​opentelemetry/sdk-logs's releases.

experimental/v0.221.0

0.221.0

💥 Breaking Changes

• 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

🚀 Features

• 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

experimental/v0.220.0

0.220.0

💥 Breaking Changes

• 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

🚀 Features

• 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

🐛 Bug Fixes

• 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

... (truncated)

Commits

• 76fa6b5 chore: prepare next release (#6942)
• 3787896 chore(deps): update dependency webpack-cli to v7.2.1 (#6934)
• be5f757 fix(deps): update dependency body-parser to v2.3.0 [security] (#6941)
• f6d8fbe chore(deps): lock file maintenance (#6559)
• 9612732 chore: remove examples/dice from workspaces (#6937)
• 7107906 chore: start using min-release-age in .npmrc, disable minimumReleaseAge for r...
• a7e5d11 chore(deps): update dependency webpack to v5.108.4 (#6933)
• af7a82d chore(deps): update dependency msw to v2.15.0 (#6831)
• b9f57c6 chore(deps): update dependency @​types/webpack-env to v1.18.8 (#6877)
• cbb4abf chore(deps): update ubuntu docker tag to v26 (#6635)
• Additional commits viewable in compare view

Updates applicationinsights from 3.11.0 to 3.16.0

Release notes

Sourced from applicationinsights's releases.

3.16.0

Other Changes

• Bumped @opentelemetry/* (0.220 / 2.9) and @azure/monitor-opentelemetry to resolve dependency audit alerts.
• Replaced the diagnostic-channel/diagnostic-channel-publishers console log collection with OpenTelemetry console instrumentation provided by @azure/monitor-opentelemetry.
• Deprecated noDiagnosticChannel and noPatchModules in favor of OpenTelemetry instrumentationOptions.
• Console severity is now derived from the console method (console.error maps to Error, console.warn maps to Warning, and console.log/console.info map to Information).
• An explicitly configured console logSendingLevel now takes precedence over APPLICATIONINSIGHTS_INSTRUMENTATION_LOGGING_LEVEL.

Release PRs

• microsoft/ApplicationInsights-node.js#1514

Full Changelog: 3.15.1...3.16.0

3.15.1

Other Changes

• Updated @azure/monitor-opentelemetry, @azure/identity, and @opentelemetry/* dependencies.
• Removed the legacy @azure/functions-old (v3) dependency.
• Resolved vulnerabilities in dependencies.

Bug Fixes

• AutoCollectExceptions no longer calls forceFlush per exception and now rate-limits exception telemetry to 50 records/min (emitting a single suppressed-count summary per window). forceFlush still runs on the terminal exit path.

Release PRs

• microsoft/ApplicationInsights-node.js#1509

Full Changelog: 3.15.0...3.15.1

3.15.0

Breaking Changes

• Minimum supported Node.js version is now 20.0.0. Node.js 18 is end-of-life (April 2025) and the underlying @azure/monitor-opentelemetry / @azure/monitor-opentelemetry-exporter dependencies require Node >= 20.

Other Changes

• Updated @azure/monitor-opentelemetry to ^1.18.0 and @azure/monitor-opentelemetry-exporter to ^1.0.0-beta.41.
• Resolved vulnerabilities in dependencies (added overrides for protobufjs ^8.2.0 and serialize-javascript ^7.0.5).

Bug Fixes

• Fix memory leak caused by process event listener accumulation when useAzureMonitor() is called multiple times. (#1415)

Release PRs

• microsoft/ApplicationInsights-node.js#1496
• microsoft/ApplicationInsights-node.js#1497

... (truncated)

Changelog

Sourced from applicationinsights's changelog.

3.16.0 (2026-08-12)

Other Changes

• Bumped @opentelemetry/* (0.220 / 2.9) and @azure/monitor-opentelemetry to resolve dependency audit alerts.
• Replaced the diagnostic-channel/diagnostic-channel-publishers console log collection with OpenTelemetry console instrumentation provided by @azure/monitor-opentelemetry.
• Deprecated noDiagnosticChannel and noPatchModules in favor of OpenTelemetry instrumentationOptions.
• Console severity is now derived from the console method (console.error maps to Error, console.warn maps to Warning, and console.log/console.info map to Information).
• An explicitly configured console logSendingLevel now takes precedence over APPLICATIONINSIGHTS_INSTRUMENTATION_LOGGING_LEVEL.

3.15.1 (2026-06-24)

Other Changes

• Updated @azure/monitor-opentelemetry, @azure/identity, and @opentelemetry/* dependencies.
• Removed the legacy @azure/functions-old (v3) dependency.
• Resolve vulnerabilities in dependencies.

Bug Fixes

• AutoCollectExceptions no longer calls forceFlush per exception and now rate-limits exception telemetry to 50 records/min (emitting a single suppressed-count summary per window). forceFlush still runs on the terminal exit path.

3.15.0 (2026-05-13)

Breaking Changes

• Minimum supported Node.js version is now 20.0.0. Node.js 18 is end-of-life (April 2025) and the underlying @azure/monitor-opentelemetry / @azure/monitor-opentelemetry-exporter dependencies require Node >= 20.

Other Changes

• Updated @​azure/monitor-opentelemetry and @​azure/monitor-opentelemetry-exporter.
• Resolve vulnerabilities in dependencies.

Bug Fixes

• Fix memory leak caused by process event listener accumulation when useAzureMonitor() is called multiple times. (#1415)

3.14.0 (2026-02-24)

Other Changes

• Update OTel global detection to wait for the customer app to initialize before detection.

3.13.0 (2026-01-16)

Other Changes

• Add OpenTelemetry global detection to the agent.
• Add functionality for the TelemetryClient to not use global providers.
• Resolve vulnerabilities in dependencies.

... (truncated)

Commits

• 28b31dd Release 3.16.0 (#1514)
• 62a08cc Pin GitHub Actions to full-length commit SHAs (#1513)
• 1e6ed63 Replace diagnostic-channel console collection with @​opentelemetry/instrumenta...
• d5dbb1d fix(deps): upgrade OpenTelemetry deps to resolve audit alerts (#1510)
• d92a053 Release 3.15.1 (#1509)
• 24d6657 fix(deps): upgrade OpenTelemetry and nyc to resolve audit vulns, drop protobu...
• b441fad perf: amortize per-sample startup and post comments on fork PRs (#1506)
• 9907aae Block preview/dev/alpha prereleases of @​azure/monitor-opentelemetry-exporter ...
• a4c4943 perf: Expand Benchmarks vs Upstream OpenTelemetry & CI Regression (#1500)
• 2bf123f Rate-limit AutoCollectExceptions and drop per-exception forceFlush (#1499)
• Additional commits viewable in compare view

[github-actions]

Performance comparison

Threshold for gating regression: -15% (median ops/s)

Scenario	Tier	Baseline (ops/s)	Candidate (ops/s)	Δ %
TrackDependencyTest	gating	453478.40	459878.40	🟢 1.41%
TrackTraceTest	gating	116559.09	116377.60	🔴 -0.16%
AzureMonitorSpanTest	gating	775577.60	778137.60	🟢 0.33%
AzureMonitorLogTest	gating	124467.20	124749.45	🟢 0.23%
OtelSpanTest	informational	103014.40	104857.60	🟢 1.79%
OtelLogTest	informational	562319.54	575731.25	🟢 2.39%

✅ No gating regression beyond threshold.

_{baseline: 2026-08-14T06:02:55.884Z (node v22.23.1, 3 samples × 5s)
candidate: 2026-08-14T05:59:48.987Z (node v22.23.1, 3 samples × 5s)}