ToC/location/UID refactor for Metrics articles

.openpublishing.redirection.json

@@ -1719,6 +1719,36 @@
             "redirect_url": "/aspnet/core/fundamentals/validation",
             "redirect_document_id": false
         },
+        {
+            "source_path": "aspnetcore/log-mon/metrics/metrics.md",
+            "redirect_url": "/aspnet/core/metrics/overview",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "aspnetcore/log-mon/metrics/built-in.md",
+            "redirect_url": "/aspnet/core/metrics/built-in",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "aspnetcore/log-mon/metrics/built-in-components.md",
+            "redirect_url": "/aspnet/core/metrics/blazor",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "aspnetcore/log-mon/metrics/built-in-diagnostics.md",
+            "redirect_url": "/aspnet/core/metrics/diagnostics",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "aspnetcore/log-mon/metrics/built-in-http.md",
+            "redirect_url": "/aspnet/core/metrics/http",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "aspnetcore/log-mon/metrics/built-in-security.md",
+            "redirect_url": "/aspnet/core/metrics/security",
+            "redirect_document_id": false
+        },
         {
             "source_path": "aspnetcore/blazor/hybrid/tutorials/maui.md",
             "redirect_url": "/dotnet/maui/get-started/first-app",

aspnetcore/blazor/performance/index.md

@@ -51,7 +51,7 @@ builder.Services.ConfigureOpenTelemetryTracerProvider(tracerProvider =>
 
 ### Performance meters
 
-For more information on the following performance meters, see <xref:log-mon/metrics/built-in>.
+For more information on the following performance meters, see <xref:metrics/built-in>.
 
 `Microsoft.AspNetCore.Components` meter:
 
@@ -74,7 +74,7 @@ In server-side Blazor apps, additional circuit-specific metrics include:
 
 ### Blazor tracing
 
-For more information on the following tracing activities, see <xref:log-mon/metrics/built-in>.
+For more information on the following tracing activities, see <xref:metrics/built-in>.
 
 The new activity tracing capabilities use the `Microsoft.AspNetCore.Components` activity source and provide three main types of tracing activities: circuit lifecycle, navigation, and event handling.
 

aspnetcore/fundamentals/servers/includes/memory-eviction2.md

@@ -8,7 +8,7 @@ In versions of .NET earlier than 10, memory allocated by the pool remains reserv
 
 The default memory pool used by the ASP.NET Core server implementations includes metrics, which can be used to monitor and analyze memory usage patterns. The metrics are under the name `"Microsoft.AspNetCore.MemoryPool"`.
 
-For information about metrics and how to use them, see <xref:log-mon/metrics/metrics>.
+For information about metrics and how to use them, see <xref:metrics/overview>.
 
 ## Manage memory pools
 

aspnetcore/fundamentals/servers/kestrel/memory-management.md

@@ -25,7 +25,7 @@ This automatic eviction feature reduces overall memory usage and helps applicati
 
 The default memory pool used by the ASP.NET Core server implementations includes metrics, which can be used to monitor and analyze memory usage patterns. The metrics are under the name `"Microsoft.AspNetCore.MemoryPool"`.
 
-For information about metrics and how to use them, see <xref:log-mon/metrics/metrics>.
+For information about metrics and how to use them, see <xref:metrics/overview>.
 
 ## Manage memory pools
 

aspnetcore/fundamentals/servers/kestrel/security-considerations.md

@@ -673,8 +673,8 @@ Beyond rejection-specific signals, Kestrel emits a set of built-in metrics under
 
 These metrics integrate with OpenTelemetry, `dotnet-counters`, Prometheus exporters, and Azure Monitor. For full setup guidance, see:
 
-- [ASP.NET Core metrics overview](xref:log-mon/metrics/metrics)
-- [Kestrel built-in metrics reference](xref:log-mon/metrics/built-in-http#microsoftaspnetcoreserverkestrel)
+- [ASP.NET Core metrics overview](xref:metrics/overview)
+- [Kestrel built-in metrics reference](xref:metrics/http#microsoftaspnetcoreserverkestrel)
 
 ### TLS-over-HTTP detection
 

aspnetcore/log-mon/metrics/built-in-components.md → aspnetcore/metrics/blazor.md

@@ -1,19 +1,19 @@
 ---
-title: ASP.NET Core built-in Blazor (Components) metrics
+title: ASP.NET Core built-in Blazor (Razor components) metrics
 ai-usage: ai-assisted
 author: guardrex
 description: Learn about built-in Blazor (Components) metrics for ASP.NET Core apps, including component, lifecycle, and server circuit metrics.
 monikerRange: '>= aspnetcore-10.0'
 ms.author: wpickett
 ms.date: 08/05/2026
 ms.topic: reference
-uid: log-mon/metrics/built-in-components
+uid: metrics/blazor
 ---
-# ASP.NET Core built-in Blazor (Components) metrics
+# ASP.NET Core built-in Blazor (Razor components) metrics
 
-This article describes the built-in Blazor (Components) metrics for ASP.NET Core produced using the <xref:System.Diagnostics.Metrics?displayProperty=nameWithType> API. These metrics cover Razor component route changes and browser events, component lifecycle events, and server-side Blazor circuits. They're available in ASP.NET Core 10.0 or later.
+This article describes the built-in Blazor (Razor components) metrics for ASP.NET Core produced using the <xref:System.Diagnostics.Metrics?displayProperty=nameWithType> API. These metrics cover Razor component route changes and browser events, component lifecycle events, and server-side Blazor circuits. They're available in ASP.NET Core 10.0 or later.
 
-For an overview of all built-in metrics reference pages and how to read this reference, see <xref:log-mon/metrics/built-in>. For information on how to collect, report, enrich, and test with ASP.NET Core metrics, see <xref:log-mon/metrics/metrics>.
+For an overview of all built-in metrics reference pages and how to read this reference, see <xref:metrics/built-in>. For information on how to collect, report, enrich, and test with ASP.NET Core metrics, see <xref:metrics/overview>.
 
 ## `Microsoft.AspNetCore.Components`
 
@@ -128,10 +128,10 @@ Usage:
 * How many sessions processed?
 * How long do users keep the session/tab open?
 
-## See also
+## Additional resources
 
-* <xref:log-mon/metrics/built-in>
-* <xref:log-mon/metrics/built-in-http>
-* <xref:log-mon/metrics/built-in-diagnostics>
-* <xref:log-mon/metrics/built-in-security>
-* <xref:log-mon/metrics/metrics>
+* <xref:metrics/built-in>
+* <xref:metrics/http>
+* <xref:metrics/diagnostics>
+* <xref:metrics/security>
+* <xref:metrics/overview>

aspnetcore/log-mon/metrics/built-in.md → aspnetcore/metrics/built-in.md

@@ -6,22 +6,22 @@ description: Learn about built-in metrics for ASP.NET Core apps.
 ms.author: wpickett
 ms.date: 08/05/2026
 ms.topic: reference
-uid: log-mon/metrics/built-in
+uid: metrics/built-in
 ---
 # ASP.NET Core built-in metrics
 
 This article is the entry point for the built-in metrics that ASP.NET Core produces using the <xref:System.Diagnostics.Metrics?displayProperty=nameWithType> API. The metrics reference is organized into focused pages by topic. Use the following pages to find the instruments, attributes, and usage guidance for each area. For a listing of metrics based on the older [EventCounters](/dotnet/core/diagnostics/event-counters) API, see [Available counters](/dotnet/core/diagnostics/available-counters).
 
-For information on how to collect, report, enrich, and test with ASP.NET Core metrics, see <xref:log-mon/metrics/metrics>.
+For information on how to collect, report, enrich, and test with ASP.NET Core metrics, see <xref:metrics/overview>.
 
 ## Metrics reference pages
 
 Page | Namespaces | Example metrics
 --- | --- | ---
-[HTTP metrics](xref:log-mon/metrics/built-in-http) | `Microsoft.AspNetCore.Hosting`, `Microsoft.AspNetCore.Routing`, `Microsoft.AspNetCore.RateLimiting`, `Microsoft.AspNetCore.HeaderParsing`, `Microsoft.AspNetCore.Server.Kestrel`, `Microsoft.AspNetCore.Http.Connections` (SignalR) | `http.server.request.duration`, `aspnetcore.routing.match_attempts`, `kestrel.active_connections`, `signalr.server.active_connections`
-[Diagnostics metrics](xref:log-mon/metrics/built-in-diagnostics) | `Microsoft.AspNetCore.Diagnostics` | `aspnetcore.diagnostics.exceptions`
-[Blazor (Components) metrics](xref:log-mon/metrics/built-in-components) | `Microsoft.AspNetCore.Components`, `Microsoft.AspNetCore.Components.Lifecycle`, `Microsoft.AspNetCore.Components.Server.Circuits` | `aspnetcore.components.navigation`, `aspnetcore.components.circuit.active`
-[Authentication and authorization metrics](xref:log-mon/metrics/built-in-security) | `Microsoft.AspNetCore.Authorization`, `Microsoft.AspNetCore.Authentication` | `aspnetcore.authorization.attempts`, `aspnetcore.authentication.challenges`
+[HTTP metrics](xref:metrics/http) | `Microsoft.AspNetCore.Hosting`, `Microsoft.AspNetCore.Routing`, `Microsoft.AspNetCore.RateLimiting`, `Microsoft.AspNetCore.HeaderParsing`, `Microsoft.AspNetCore.Server.Kestrel`, `Microsoft.AspNetCore.Http.Connections` (SignalR) | `http.server.request.duration`, `aspnetcore.routing.match_attempts`, `kestrel.active_connections`, `signalr.server.active_connections`
+[Diagnostics metrics](xref:metrics/diagnostics) | `Microsoft.AspNetCore.Diagnostics` | `aspnetcore.diagnostics.exceptions`
+[Blazor (Components) metrics](xref:metrics/blazor) | `Microsoft.AspNetCore.Components`, `Microsoft.AspNetCore.Components.Lifecycle`, `Microsoft.AspNetCore.Components.Server.Circuits` | `aspnetcore.components.navigation`, `aspnetcore.components.circuit.active`
+[Authentication and authorization metrics](xref:metrics/security) | `Microsoft.AspNetCore.Authorization`, `Microsoft.AspNetCore.Authentication` | `aspnetcore.authorization.attempts`, `aspnetcore.authentication.challenges`
 
 The Blazor (Components) and authentication and authorization metrics pages describe metrics available in ASP.NET Core 10.0 or later. Select ASP.NET Core 10.0 (or a later version) with the version selector to view that content.
 
@@ -45,4 +45,4 @@ Each metric on the reference pages is documented with the following information:
 * **Presence**: When the attribute is present, for example `Always` or only under specific conditions.
 * **Usage**: Example questions the metric helps answer.
 
-For guidance on how to collect, report, enrich, and test with these metrics, see <xref:log-mon/metrics/metrics>.
+For guidance on how to collect, report, enrich, and test with these metrics, see <xref:metrics/overview>.

aspnetcore/log-mon/metrics/built-in-diagnostics.md → aspnetcore/metrics/diagnostics.md

@@ -6,13 +6,13 @@ description: Learn about built-in diagnostics metrics for ASP.NET Core apps, rep
 ms.author: wpickett
 ms.date: 08/05/2026
 ms.topic: reference
-uid: log-mon/metrics/built-in-diagnostics
+uid: metrics/diagnostics
 ---
 # ASP.NET Core built-in diagnostics metrics
 
 This article describes the built-in diagnostics metrics for ASP.NET Core produced using the <xref:System.Diagnostics.Metrics?displayProperty=nameWithType> API. These metrics report diagnostics information from the ASP.NET Core error handling middleware.
 
-For an overview of all built-in metrics reference pages and how to read this reference, see <xref:log-mon/metrics/built-in>. For information on how to collect, report, enrich, and test with ASP.NET Core metrics, see <xref:log-mon/metrics/metrics>.
+For an overview of all built-in metrics reference pages and how to read this reference, see <xref:metrics/built-in>. For information on how to collect, report, enrich, and test with ASP.NET Core metrics, see <xref:metrics/overview>.
 
 ## `Microsoft.AspNetCore.Diagnostics`
 
@@ -32,10 +32,10 @@ Attribute | Type | Description | Examples | Presence
 `aspnetcore.diagnostics.handler.type` | string | Full type name of the [`IExceptionHandler`](/dotnet/api/microsoft.aspnetcore.diagnostics.iexceptionhandler) implementation that handled the exception. | `Contoso.MyHandler` | If the exception was handled by this handler.
 `exception.type` | string | The full name of exception type. | `System.OperationCanceledException`; `Contoso.MyException` | Always
 
-## See also
+## Additional resources
 
-* <xref:log-mon/metrics/built-in>
-* <xref:log-mon/metrics/built-in-http>
-* <xref:log-mon/metrics/built-in-components>
-* <xref:log-mon/metrics/built-in-security>
-* <xref:log-mon/metrics/metrics>
+* <xref:metrics/built-in>
+* <xref:metrics/http>
+* <xref:metrics/blazor>
+* <xref:metrics/security>
+* <xref:metrics/overview>

aspnetcore/log-mon/metrics/built-in-http.md → aspnetcore/metrics/http.md

@@ -6,13 +6,13 @@ description: Learn about built-in HTTP metrics for ASP.NET Core apps, including
 ms.author: wpickett
 ms.date: 08/05/2026
 ms.topic: reference
-uid: log-mon/metrics/built-in-http
+uid: metrics/http
 ---
 # ASP.NET Core built-in HTTP metrics
 
 This article describes the built-in HTTP-related metrics for ASP.NET Core produced using the <xref:System.Diagnostics.Metrics?displayProperty=nameWithType> API. These metrics cover hosting, routing, rate limiting, header parsing, the Kestrel web server, and SignalR.
 
-For an overview of all built-in metrics reference pages and how to read this reference, see <xref:log-mon/metrics/built-in>. For information on how to collect, report, enrich, and test with ASP.NET Core metrics, see <xref:log-mon/metrics/metrics>.
+For an overview of all built-in metrics reference pages and how to read this reference, see <xref:metrics/built-in>. For information on how to collect, report, enrich, and test with ASP.NET Core metrics, see <xref:metrics/overview>.
 
 ## `Microsoft.AspNetCore.Hosting`
 
@@ -356,10 +356,10 @@ Attribute | Type | Description | Examples | Presence
 `signalr.connection.status` | string | SignalR HTTP connection closure status. | `app_shutdown`; `timeout` | Always
 `signalr.transport` | string | [SignalR transport type](https://github.com/dotnet/aspnetcore/blob/main/src/SignalR/docs/specs/TransportProtocols.md) | `web_sockets`; `long_polling` | Always
 
-## See also
+## Additional resources
 
-* <xref:log-mon/metrics/built-in>
-* <xref:log-mon/metrics/built-in-diagnostics>
-* <xref:log-mon/metrics/built-in-components>
-* <xref:log-mon/metrics/built-in-security>
-* <xref:log-mon/metrics/metrics>
+* <xref:metrics/built-in>
+* <xref:metrics/diagnostics>
+* <xref:metrics/blazor>
+* <xref:metrics/security>
+* <xref:metrics/overview>