azure-functions-host icon indicating copy to clipboard operation
azure-functions-host copied to clipboard
verified publisher icon Azure

OTel related nuget package update.

Open RohitRanjanMS opened this issue 8 months ago • 2 comments

  • Updating the following packages System.Diagnostics.DiagnosticSource 8.0.0 -> 9.0.4 Microsoft.Extensions.Hosting.Abstractions 8.0.0 -> 9.0.4 OpenTelemetry related packages

  • Removing dependency on Azure.Monitor.OpenTelemetry.AspNetCore as the LiveMetrics support is now available in Azure.Monitor.OpenTelemetry.Exporter 1.4.0-beta.3

  • Adding InvocationId in the tags

Changed: - Azure.Monitor.OpenTelemetry.Exporter.dll: 1.3.0.0/1.300.24.10803 -> 1.4.0.0/1.400.25.20103 - Microsoft.Extensions.Configuration.Binder.dll: 8.0.0.0/8.0.123.58001 -> 9.0.0.0/9.0.24.52809 - OpenTelemetry.Api.dll: 1.0.0.0/1.9.0.1312 -> 1.0.0.0/1.11.2.1586 - OpenTelemetry.Api.ProviderBuilderExtensions.dll: 1.0.0.0/1.9.0.1312 -> 1.0.0.0/1.11.2.1586 - OpenTelemetry.dll: 1.0.0.0/1.9.0.1312 -> 1.0.0.0/1.11.2.1586 - OpenTelemetry.Exporter.OpenTelemetryProtocol.dll: 1.0.0.0/1.9.0.1312 -> 1.0.0.0/1.11.2.1586 - OpenTelemetry.Extensions.Hosting.dll: 1.0.0.0/1.9.0.1312 -> 1.0.0.0/1.11.2.1586 - OpenTelemetry.Instrumentation.AspNetCore.dll: 1.9.0.42/1.9.0.42 -> 1.11.1.401/1.11.1.401 - OpenTelemetry.Instrumentation.Http.dll: 1.9.0.41/1.9.0.41 -> 1.11.1.407/1.11.1.407 - OpenTelemetry.PersistentStorage.Abstractions.dll: 1.0.0.0/1.0.0.0 -> 1.0.1.378/1.0.1.378 - OpenTelemetry.PersistentStorage.FileSystem.dll: 1.0.0.0/1.0.0.0 -> 1.0.1.378/1.0.1.378

Removed: - Azure.Monitor.OpenTelemetry.AspNetCore.dll: 1.2.0.0/1.200.24.16203 - Azure.Monitor.OpenTelemetry.LiveMetrics.dll: 1.0.0.0/1.0.24.15803 - OpenTelemetry.Exporter.Console.dll: 1.0.0.0/1.6.0.1006 - System.Text.Json.dll: 8.0.0.0/8.0.1024.46610

Added: - Microsoft.Extensions.Configuration.Abstractions.dll: 9.0.0.0/9.0.425.16305 - Microsoft.Extensions.Configuration.dll: 9.0.0.0/9.0.24.52809 - Microsoft.Extensions.DependencyInjection.Abstractions.dll: 9.0.0.0/9.0.425.16305 - Microsoft.Extensions.DependencyInjection.dll: 9.0.0.0/9.0.24.52809 - Microsoft.Extensions.Diagnostics.Abstractions.dll: 9.0.0.0/9.0.425.16305 - Microsoft.Extensions.FileProviders.Abstractions.dll: 9.0.0.0/9.0.425.16305 - Microsoft.Extensions.Hosting.Abstractions.dll: 9.0.0.0/9.0.425.16305 - Microsoft.Extensions.Logging.Abstractions.dll: 9.0.0.0/9.0.425.16305 - Microsoft.Extensions.Logging.Configuration.dll: 9.0.0.0/9.0.24.52809 - Microsoft.Extensions.Logging.dll: 9.0.0.0/9.0.24.52809 - Microsoft.Extensions.Options.ConfigurationExtensions.dll: 9.0.0.0/9.0.24.52809 - Microsoft.Extensions.Options.dll: 9.0.0.0/9.0.425.16305 - Microsoft.Extensions.Primitives.dll: 9.0.0.0/9.0.425.16305 - OpenTelemetry.Instrumentation.Process.dll: 1.11.0.408/1.11.0.408 - OpenTelemetry.Instrumentation.Runtime.dll: 1.11.1.410/1.11.1.410 - System.Diagnostics.DiagnosticSource.dll: 9.0.0.0/9.0.425.16305

IMPORTANT: Currently, changes must be backported to the in-proc branch to be included in Core Tools and non-Flex deployments.

  • [x] Backporting to the in-proc branch is not required
    • Otherwise: Link to backporting PR
  • [x] My changes do not require documentation changes
    • [ ] Otherwise: Documentation issue linked to PR
  • [ ] My changes should not be added to the release notes for the next release
    • [x] Otherwise: I've added my notes to release_notes.md
  • [x] My changes do not need to be backported to a previous version
    • [ ] Otherwise: Backport tracked by issue/PR #issue_or_pr
  • [x] My changes do not require diagnostic events changes
    • Otherwise: I have added/updated all related diagnostic events and their documentation (Documentation issue linked to PR)
  • [x] I have added all required tests (Unit tests, E2E tests)

Additional information

Additional PR information

RohitRanjanMS avatar Apr 24 '25 22:04 RohitRanjanMS

Updated runtimeassemblies.json and PR description.

RohitRanjanMS avatar Apr 25 '25 22:04 RohitRanjanMS

@RohitRanjanMS with the list above, we'll need additional reviews of the dependencies. I'm also concerned about the fact that I don't see matching removals in runtimeassemblies.json for the assemblies marked as removed. If the policy was missed when those were added, we need to decide how we want to move forward and whether we can really have those dependencies removed.

The added list doesn't seem accurate, but this might be an issue with the test detection.

fabiocav avatar Apr 26 '25 03:04 fabiocav