chore(deps): update dependency azure.monitor.opentelemetry.exporter to 1.10.0

[Workleap IT (Infra-Workleap)]

This PR contains the following updates:

Package	Change	Age	Confidence
Azure.Monitor.OpenTelemetry.Exporter (source)	1.6.0 → 1.10.0

---

Release Notes

Azure/azure-sdk-for-net (Azure.Monitor.OpenTelemetry.Exporter)

v1.10.0

Compare Source

1.10.0 (2026-10-05)

Features Added

• Added the Azure.Monitor.OpenTelemetry.Exporter.StorageSubDirectory AppContext value, settable with AppContext.SetData or a runtimeconfig.json configProperty, so that the processes or entry points of one application can share a persistent storage directory. By default the directory name is derived from the process name and AppContext.BaseDirectory, which splits storage when components of one application differ in either, and a component that runs rarely never drains its backlog. When set, the value replaces those two inputs; the instrumentation key and user name still contribute, so different users and resources stay isolated. Behaviour is unchanged when the value is not set.
  (#​62997)

Bugs Fixed

• SDK statistics sent to the Microsoft OpenTelemetry distro's configured ingestion endpoint (the Azure.Monitor.OpenTelemetry.Exporter.RouteSdkStatsToDistroEndpoint AppContext switch) now carry the same region-matched SDK statistics instrumentation key as the existing SDK statistics endpoint, instead of an all-zero placeholder. Only the destination differs on the distro path.
  (#​63342)

v1.9.0

Compare Source

1.9.0 (2026-09-04)

Features Added

• Add support for project id attributes propagation
  (#​62052)

• Shutting down a provider (including Dispose()) now writes pending telemetry to offline storage and uploads it in the background instead of blocking on ingestion. Short-lived applications such as CLI tools previously lost this telemetry, because they exit before a transmission completes; the telemetry is now durable before exit, and delivery is completed by a background drain in this or a subsequent run. ForceFlush is unchanged by default and can be opted in with the Azure.Monitor.OpenTelemetry.Exporter.PersistOnForceFlush AppContext switch, which applies to traces and logs only: a metric reader cannot distinguish a caller's flush from its periodic collection, so metric ForceFlush always transmits. The previous behavior can be restored with the Azure.Monitor.OpenTelemetry.Exporter.DisablePersistOnShutdown AppContext switch.
  (#​61818)

• How long shutdown waits for that background drain can now be set through the Azure.Monitor.OpenTelemetry.Exporter.ShutdownDrainBudgetMilliseconds AppContext data value, using either AppContext.SetData or a runtimeconfig.json configProperty. Dispose() passes a finite timeout, so by default part of that window is spent delivering telemetry and process exit tracks ingestion latency. Short-lived applications should set this to 0, which makes exit cost only the file write: measured at 2.7 ms regardless of ingestion latency, against 2011 ms with a two second ingestion delay. The default is unchanged, so long-running services keep delivering their final batch within the window Dispose() allows. A single-run CI job, where no later run exists to drain storage, should not raise this value but set the Azure.Monitor.OpenTelemetry.Exporter.DisablePersistOnShutdown switch with a bounded Retry.NetworkTimeout: raising the budget cannot guarantee delivery, because Shutdown() waits on the drain for no time at all and Dispose() is capped by the five second grace period OpenTelemetry allows it.
  (#​62340)

Bugs Fixed

• Telemetry left in offline storage by a process that exited during a transmission is no longer stranded permanently. A leased blob is renamed so that it matches neither the storage provider's blob enumeration nor its retention sweep, and the provider only reclaims those leases on a two minute maintenance timer that a short-lived process never reaches. Expired leases are now reclaimed when storage is drained.
  (#​61818)

• Offline storage is now drained shortly after startup rather than only after the process has been running for two minutes, so telemetry persisted by a previous run is uploaded even when no single run is long-lived.
  (#​61818)

• Telemetry is no longer dropped when the offline storage directory reaches its size cap. The oldest stored telemetry is evicted to make room.
  (#​61818)

• Statsbeat no longer holds up process exit. It exports once more as its meter provider is disposed, which put an ingestion round trip on the exit path; that final export now runs in the background, and its network timeout is bounded at five seconds rather than the pipeline default of 100 seconds. The customer SDK stats meter provider is instead left to live for the process lifetime, so it never exports on the exit path at all; its stats are delivered by its own periodic reader.
  (#​62340)

• Log fields are now culture-invariant. (#​61996)

• Added the telemetrySuccess dimension to Item_Dropped_Count for request and dependency telemetry.
  (#​62081)

Other Changes

• Updated OpenTelemetry dependencies to 1.18.0 and OpenTelemetry.PersistentStorage.FileSystem to 1.1.1.
  (#​62698)

• Improved activity conversion performance by reading recognized attributes from a fixed index instead of scanning the tag list for each one. Every span shape converts faster, by about a third for spans carrying Application Insights override attributes, and each conversion rents fewer pooled buffers. Standard metrics no longer collect the tags they never read.
  (#​62614)

  • Fixed pooled tag buffers being leaked whenever converting an activity failed, and retaining tag keys and values after being returned to the pool.
  • Fixed the buffer rent size being process-wide mutable state written without synchronization.
  • Fixed an activity tag with a null key dropping the remaining tags from custom properties.
  • Removed two attribute lookups that could never match. http.server_name and server.socket.address are still exported as custom properties, unchanged.

v1.8.3

Compare Source

1.8.3 (2026-07-24)

Bugs Fixed

• Hardened ingestion and Live Metrics redirect handling to reject untrusted destinations before replaying telemetry or caching the redirect. Redirect targets must now use HTTPS and match an approved Azure Monitor trust boundary, preventing credentials and telemetry from being forwarded to attacker-controlled endpoints.
  (#​61244)

Other Changes

• Customer SDK stats are now on by default; opt out with APPLICATIONINSIGHTS_SDKSTATS_DISABLED=true. dropCode/retryCode dimension values now use the spec's SCREAMING_SNAKE_CASE (e.g. CLIENT_EXCEPTION).

v1.8.2

Compare Source

1.8.2 (2026-06-30)

Features Added

• Added support for the Microsoft OpenTelemetry distro's SDK statistics: a new internal meter subscription and an AppContext switch (Azure.Monitor.OpenTelemetry.Exporter.RouteSdkStatsToDistroEndpoint) that lets the distro redirect SDK statistics to its own ingestion path. The ingestion destination and an on/off signal are resolved at startup by fetching a remote configuration; on success the configured destination is used, an explicit remote disable signal turns SDK statistics off, and any other outcome falls back to the existing region-derived ingestion endpoint so SDK statistics keep flowing. The AppContext switch has no effect on Statsbeat for callers that do not opt in.
  (#​59811)

• Subscribed the Statsbeat MeterProvider to the Microsoft OpenTelemetry distro's Network SDKStats meter (MicrosoftOpenTelemetryNetworkSdkStatsMeter) so distro-emitted Network statistics flow through the existing Statsbeat cadence when the distro runs with a non-Azure-Monitor exporter.
  (#​60209)

• Subscribed the Statsbeat MeterProvider to the Microsoft OpenTelemetry distro's Feature SDKStats meter (MicrosoftOpenTelemetryFeatureSdkStatsMeter) so distro-emitted Feature statistics reach the Statsbeat ingestion path. The distro uses an independent, spec-aligned bit map to avoid collisions with the classic Application Insights SDK's FeatureStatsbeatMeter.
  (#​59529)

• Added Network SDKStats reporting, emitting the short-interval Network statistics defined in the Application Insights SDKStats spec on a 15-minute cadence: Request_Success_Count, Request_Failure_Count, Request_Duration, Retry_Count, Throttle_Count, and Exception_Count, each with the spec-defined dimensions (including host, statusCode, and exceptionType).
  (#​59909, #​60018)

Other Changes

• Updated customer SDK stats dimension key names to use camelCase (computeType, telemetryType, dropCode, dropReason, retryCode, retryReason).
  (#​59902)

v1.8.1

Compare Source

1.8.1 (2026-05-20)

Features Added

• Added GenAI main agent attribution support. Automatically propagates microsoft.gen_ai.main_agent.* attributes from parent spans to child spans and log records, enabling end-to-end tracing of AI agent orchestration.
  (#​59368)

v1.8.0

Compare Source

1.8.0 (2026-04-29)

Other Changes

• Pulled in OpenTelemetry dependency updates.

v1.7.0

Compare Source

1.7.0 (2026-03-27)

Features Added

• Added ApplicationInsightsRestClientSettings to support creating a ApplicationInsightsRestClient from IConfiguration, including configuration-based credential resolution and dependency injection registration.
  (#​56891)

Bugs Fixed

• Fixed AOT warning regression by using the source generator for ConfigurationBinder calls.
  (#​56368)

Other Changes

• Update OpenTelemetry dependencies
  • OpenTelemetry 1.15.1
  • OpenTelemetry.Extensions.Hosting 1.15.1
    (#​57549)
• Made AzureMonitorLogExporter, AzureMonitorMetricExporter, and AzureMonitorTraceExporter public for direct use when configuring OpenTelemetry.
  (#​56344)
• Made options EnablePerformanceCounters and EnableStandardMetrics public in AzureMonitorExporterOptions.
  (#​56344)

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate CLI.

[Workleap IT (Infra-Workleap)]

Branch automerge failure

This PR was configured for branch automerge. However, this is not possible, so it has been raised as a PR instead.

---

• Branch has one or more failed status checks

[Copilot]

Pull request overview

Updates the Leap CLI project’s telemetry exporter dependency to the latest Azure Monitor OpenTelemetry exporter version, aligning the tool with upstream OpenTelemetry dependency updates.

Changes:

• Bump Azure.Monitor.OpenTelemetry.Exporter from 1.6.0 to 1.8.0 in the CLI project.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.