Looking for Clarification on HTTP Stable Semantic Convention support.

[TylerHelmuth]

I'm trying to understand exactly which packages are submitting stable HTTP semantic conventions. Is this table accurate?

Instrumentation	OTEL_SEMCONV_STABILITY_OPT_IN supported	http/dup supported	Only Stable HTTP SemConv Emitted
OpenTelemetry.Instrumentation.AspNetCore	1.5.1-beta.1 - 1.6.0-beta.3	YES	1.6.0-rc.1/1.6.0
OpenTelemetry.Instrumentation.Http	1.5.1-beta.1 - 1.6.0-beta.3	YES	1.6.0-rc.1/1.6.0
OpenTelemetry.Instrumentation.AspNet.TelemetryHttpModule	NO	NO	NO
OpenTelemetry.Instrumentation.AspNet	NO	NO	1.7.0-beta.1
OpenTelemetry .NET Automatic Instrumentation Agent	v1.0.0-rc.1 - Latest	YES	NO

[vishweshbankwar]

@TylerHelmuth OpenTelemetry.Instrumentation.AspNetCore and OpenTelemetry.Instrumentation.Http details are correct in the table.

For OpenTelemetry.Instrumentation.AspNet - Please ask the question on https://github.com/open-telemetry/opentelemetry-dotnet-contrib since it is part of that repo.

For OpenTelemetry .NET Automatic Instrumentation Agent - Reach out to https://github.com/open-telemetry/opentelemetry-dotnet-instrumentation

[Kielek]

@TylerHelmuth, OpenTelemetry .NET Automatic Instrumentation ~~Agent~~ - please check list of dependencies related to the OpenTelemetry.Instrumentation.* packages. Http sem. conv. i mostly related to these libraries.

Versions can be found in https://github.com/open-telemetry/opentelemetry-dotnet-instrumentation/blob/main/CHANGELOG.md

[Kielek]

Closing. Migration to new sem. conv. seems to be done.

@TylerHelmuth, please reopen/comment if you need more help here.