API proposal for Blazor diagnostics DI

[javiercn]

Background and Motivation

We are adding metrics and distributed tracing for Blazor.
We need to add the new services to the dependency injection.
This registration doesn't enable the metrics or traces by default.
The API is in Infrastructure namespace, it's not expected to be called by external code.

Proposed API

namespace Microsoft.AspNetCore.Components.Infrastructure
{
+    public static class ComponentsMetricsServiceCollectionExtensions
+    {
+        public static IServiceCollection AddComponentsMetrics(IServiceCollection services)
+        public static IServiceCollection AddComponentsTracing(IServiceCollection services)
+    }
}

Alternative API

namespace Microsoft.AspNetCore.Components.Infrastructure
{
+    public static class ComponentsDiagnosticsServiceCollectionExtensions
+    {
+        public static IServiceCollection AddComponentsMetrics(IServiceCollection services)
+        public static IServiceCollection AddComponentsTracing(IServiceCollection services)
+    }
}

Usage Examples - in the internal DI code of Blazor

namespace Microsoft.Extensions.DependencyInjection;

public static class RazorComponentsServiceCollectionExtensions
{
    public static IRazorComponentsBuilder AddRazorComponents(this IServiceCollection services, Action<RazorComponentsServiceOptions>? configure = null)
    {
        ComponentsMetricsServiceCollectionExtensions.AddComponentsMetrics(services);
        ComponentsMetricsServiceCollectionExtensions.AddComponentsTracing(services);
    }

[dotnet-policy-service]

Thank you for submitting this for API review. This will be reviewed by @dotnet/aspnet-api-review at the next meeting of the ASP.NET Core API Review group. Please ensure you take a look at the API review process documentation and ensure that:

• The PR contains changes to the reference-assembly that describe the API change. Or, you have included a snippet of reference-assembly-style code that illustrates the API change.
• The PR describes the impact to users, both positive (useful new APIs) and negative (breaking changes).
• Someone is assigned to "champion" this change in the meeting, and they understand the impact and design of the change.

[javiercn]

No changes