This repository is for active development of the Azure SDK for .NET. For consumers of the SDK we recommend visiting our public developer docs at https://learn.microsoft.com/dotnet/azure/ or our versioned developer docs at https://azure.github.io/azure-sdk-for-net.
When we shipped v1 of the Azure Monitor Exporter, we had mapping for the Experimental version OpenTelemetry Http Semantic Conventions. When OpenTelemetry stabilized the spec for Http Semantic Conventions, we immediately update the mappings in the Exporter, but we needed to maintain compatibility for the Experimental attributes.
Most users will never notice the change because these attributes are set by the OpenTelemetry Instrumentation libraries.
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @cijothomas @rajkumar-rangaraj @reyang @TimothyMothra @vishweshbankwar.
Library name
Azure.Monitor.OpenTelemetry.Exporter
Please describe the feature.
When we shipped v1 of the Azure Monitor Exporter, we had mapping for the Experimental version OpenTelemetry Http Semantic Conventions. When OpenTelemetry stabilized the spec for Http Semantic Conventions, we immediately update the mappings in the Exporter, but we needed to maintain compatibility for the Experimental attributes.
Most users will never notice the change because these attributes are set by the OpenTelemetry Instrumentation libraries.
References
Semantic Conventions for HTTP Spans: https://github.com/open-telemetry/semantic-conventions/blob/main/docs/http/http-spans.md
https://github.com/Azure/azure-sdk-for-net/blob/2944f6eb233d5487572bfde399d96b5fcc993944/sdk/monitor/Azure.Monitor.OpenTelemetry.Exporter/src/Internals/ActivityTagsProcessor.cs#L17-L39
https://github.com/Azure/azure-sdk-for-net/blob/2944f6eb233d5487572bfde399d96b5fcc993944/sdk/monitor/Azure.Monitor.OpenTelemetry.Exporter/src/Customizations/Models/RemoteDependencyData.cs#L63-L82