[dependabot]

Bumps applicationinsights from 3.10.0 to 3.17.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: microsoft/ApplicationInsights-node.js@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: microsoft/ApplicationInsights-node.js@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.17.0 (2026-10-06)

Breaking Changes

• Minimum supported Node.js version is now 22.0.0, matching the Azure Monitor OpenTelemetry dependencies.
• Database telemetry now follows the stable OpenTelemetry database semantic conventions introduced by the updated instrumentations. Dependency names can change from legacy values such as mongodb.insert to low-cardinality names such as insert <collection> or createIndexes <namespace>. Update alerts, dashboards, and queries that match exact database dependency names.

Telemetry Changes

• Database spans now use db.system.name, db.namespace, db.query.text, and db.operation.name instead of the deprecated db.system, db.name, db.statement, and db.operation attributes.
• @azure/monitor-opentelemetry-exporter 1.0.0-beta.46 maps the stable database attributes to Application Insights dependency type, target, and data fields. Attributes consumed by that mapping are no longer duplicated in custom properties.
• HTTP instrumentation can provide the request method as the span name and carry the path in route or URL attributes. Azure Monitor derives the Application Insights request name from the method and route or URL when those attributes are available.

Other Changes

• Updated @azure/monitor-opentelemetry to 1.20.1 and @azure/monitor-opentelemetry-exporter to 1.0.0-beta.46.
• Added Azure Container Apps resource detection and programmatic console log severity configuration through the updated Azure Monitor distribution.
• Included Azure Monitor fixes for performance-counter sampling, resource detector dependencies, OTEL_BSP_* environment variable handling, instrumentation lifecycle, Live Metrics recovery, and stable OpenTelemetry database attributes.
• Updated OpenTelemetry dependencies to stable 2.10.0 and experimental 0.221.0.
• Refreshed performance harness dependencies to resolve npm audit vulnerabilities.

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

... (truncated)

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)