First stable release of AspNetCore and Http instrumentation libraries

[utpilla]

We're excited to announce the release of stable support for OpenTelemetry.Instrumentation.Http and OpenTelemetry.Instrumentation.AspNetCore.

Key changes in stable version

OpenTelemetry.Instrumentation.Http and OpenTelemetry.Instrumentation.AspNetCore

Removal of support for OTEL_SEMCONV_STABILITY_OPT_IN. Both instrumentations now default to emitting the stable HTTP semantic conventions.

OpenTelemetry.Instrumentation.AspNetCore

The gRPC server instrumentation will no longer be enabled by default in OpenTelemetry.Instrumentation.AspNetCore. It is now provided as an opt-in experimental feature.

FAQs

1. What should we do if we still need the older conventions emitted by
   instrumentation libraries?
   You can continue to use version 1.6.0-beta.3 of the instrumentation libraries. However, please note that any reported issues related to older conventions will not be fixed.
2. What are the attributes that are emitted by instrumentation libraries?
   Refer to Readme.md for OpenTelemetry.Instrumentation.Http and OpenTelemetry.Instrumentation.AspNetCore for the complete list of attributes that are emitted by default for both Traces and Metrics.
3. There are two stable versions available 1.6.0 and 1.7.0, what is the difference?
   There is no difference in terms of functionality between versions. We recommend using the latest stable version, i.e., 1.7.0. The difference lies in the package dependencies: 1.7.0 depends on OpenTelemetry.Api.ProviderBuilderExtensions version >=1.7.0, which requires >=8.0.0 version of System.Diagnostics.DiagnosticSource. On the other hand, 1.6.0 depends on OpenTelemetry.Api.ProviderBuilderExtensions version >=1.6.0, which brings in >=7.0.0 version of System.Diagnostics.DiagnosticSource.

For more detailed information, please review the changelogs for corresponding libraries.