Apologies if this is the wrong location and/or format for this issue, but I wasn't sure where to put it. 🙂
This request comes up because of this issue we had opened in the OpenTelemetry .NET SDK repo: open-telemetry/opentelemetry-dotnet#7426
In ASP.NET Core 11, my understanding is that the intention is that ASP.NET Core itself will be fully-compliant with the required parts of the HTTP Server Semantic Conventions.
When that's achieved, the use of the existing OpenTelemetry.Instrumentation.AspNetCore NuGet package would become optional to get compliant metrics and traces.
However, the linked issue shows an application where a user tried to achieve this and had difficultly getting the right outcome in their application.
We can improve our documentation on the OpenTelemetry guide to help users with this scenario, but would it make sense as part of the ASP.NET Core 11 release to have similar documentation on the ASP.NET Core side given this scenario would become more common?
/cc @danroth27
Article level tracking issues tied to this parent issue:
Built-in metrics reference (Hosting meter) aspnetcore/log-mon/metrics/built-in.md -- Tracking issue: #37272
Apologies if this is the wrong location and/or format for this issue, but I wasn't sure where to put it. 🙂
This request comes up because of this issue we had opened in the OpenTelemetry .NET SDK repo: open-telemetry/opentelemetry-dotnet#7426
In ASP.NET Core 11, my understanding is that the intention is that ASP.NET Core itself will be fully-compliant with the required parts of the HTTP Server Semantic Conventions.
When that's achieved, the use of the existing OpenTelemetry.Instrumentation.AspNetCore NuGet package would become optional to get compliant metrics and traces.
However, the linked issue shows an application where a user tried to achieve this and had difficultly getting the right outcome in their application.
We can improve our documentation on the OpenTelemetry guide to help users with this scenario, but would it make sense as part of the ASP.NET Core 11 release to have similar documentation on the ASP.NET Core side given this scenario would become more common?
/cc @danroth27
Article level tracking issues tied to this parent issue:
Built-in metrics reference (Hosting meter) aspnetcore/log-mon/metrics/built-in.md -- Tracking issue: #37272