Update logging docs

.openpublishing.redirection.core.json

@@ -1165,6 +1165,42 @@
             "source_path_from_root": "/docs/core/extensions/dependency-injection-usage.md",
             "redirect_url": "/dotnet/core/extensions/dependency-injection/usage"
         },
+        {
+            "source_path_from_root": "/docs/core/extensions/high-performance-logging.md",
+            "redirect_url": "/dotnet/core/extensions/logging/high-performance-logging"
+        },
+        {
+            "source_path_from_root": "/docs/core/extensions/console-log-formatter.md",
+            "redirect_url": "/dotnet/core/extensions/logging/console-log-formatter"
+        },
+        {
+            "source_path_from_root": "/docs/core/extensions/custom-logging-provider.md",
+            "redirect_url": "/dotnet/core/extensions/logging/custom-provider"
+        },
+        {
+            "source_path_from_root": "/docs/core/extensions/logging-library-authors.md",
+            "redirect_url": "/dotnet/core/extensions/logging/library-guidance"
+        },
+        {
+            "source_path_from_root": "/docs/core/extensions/log-buffering.md",
+            "redirect_url": "/dotnet/core/extensions/logging/log-buffering"
+        },
+        {
+            "source_path_from_root": "/docs/core/extensions/log-sampling.md",
+            "redirect_url": "/dotnet/core/extensions/logging/log-sampling"
+        },
+        {
+            "source_path_from_root": "/docs/core/extensions/logging.md",
+            "redirect_url": "/dotnet/core/extensions/logging/overview"
+        },
+        {
+            "source_path_from_root": "/docs/core/extensions/logging-providers.md",
+            "redirect_url": "/dotnet/core/extensions/logging/providers"
+        },
+        {
+            "source_path_from_root": "/docs/core/extensions/logger-message-generator.md",
+            "redirect_url": "/dotnet/core/extensions/logging/source-generation"
+        },
         {
             "source_path_from_root": "/docs/core/getting-started.md",
             "redirect_url": "/dotnet/core/get-started",

docs/core/diagnostics/diagnostic-resource-monitoring.md

@@ -14,7 +14,7 @@ The measurements can be consumed in two ways:
 - Using the <xref:Microsoft.Extensions.Diagnostics.ResourceMonitoring.IResourceMonitor> interface. This interface is deprecated, so use the metrics-based approach instead. If you still need to listen to metric values manually, see [Migrate to metrics-based resource monitoring](#migrate-to-metrics-based-resource-monitoring).
 
 > [!IMPORTANT]
-> The <xref:Microsoft.Extensions.Diagnostics.ResourceMonitoring?displayProperty=fullName> package assumes that the consumer will register logging providers with the `Microsoft.Extensions.Logging` package. If you don't register logging, the call to `AddResourceMonitoring` will throw an exception. Furthermore, you can enable internal library logging by configuring the [`Debug`](xref:Microsoft.Extensions.Logging.LogLevel.Debug) log level for the `Microsoft.Extensions.Diagnostics.ResourceMonitoring` category as per the [guide](../extensions/logging.md#log-category).
+> The <xref:Microsoft.Extensions.Diagnostics.ResourceMonitoring?displayProperty=fullName> package assumes that the consumer will register logging providers with the `Microsoft.Extensions.Logging` package. If you don't register logging, the call to `AddResourceMonitoring` will throw an exception. Furthermore, you can enable internal library logging by configuring the [`Debug`](xref:Microsoft.Extensions.Logging.LogLevel.Debug) log level for the `Microsoft.Extensions.Diagnostics.ResourceMonitoring` category as per the [guide](../extensions/logging/overview.md#log-category).
 
 ## Use .NET metrics of resource monitoring
 

docs/core/diagnostics/index.md

@@ -31,7 +31,7 @@ Instrumentation is code that is added to a software project to record what it is
 
 [Logging](logging-tracing.md) is a technique where code is instrumented to produce a log, a record of interesting events that occurred while the program was running. Often a baseline set of log events are configured on by default and more extensive logging can be enabled on-demand to diagnose particular problems. Performance overhead is variable depending on how much data is being logged.
 
-For most cases, whether adding logging to an existing project or creating a new project, the [ILogger infrastructure](../extensions/logging.md) is a good default choice. `ILogger` supports fast structured logging, flexible configuration, and a collection of [common sinks](../extensions/logging-providers.md#built-in-logging-providers) including the console, which is what you see when running an ASP.NET app. Additionally, the `ILogger` interface can also serve as a facade over many [third party logging implementations](../extensions/logging-providers.md#third-party-logging-providers) that offer rich functionality and extensibility.
+For most cases, whether adding logging to an existing project or creating a new project, the [ILogger infrastructure](../extensions/logging/overview.md) is a good default choice. `ILogger` supports fast structured logging, flexible configuration, and a collection of [common sinks](../extensions/logging/providers.md#built-in-logging-providers) including the console, which is what you see when running an ASP.NET app. Additionally, the `ILogger` interface can also serve as a facade over many [third party logging implementations](../extensions/logging/providers.md#third-party-logging-providers) that offer rich functionality and extensibility.
 
 ### Metrics
 

docs/core/diagnostics/logging-tracing.md

@@ -14,7 +14,7 @@ Code can be instrumented to produce a log, which serves as a record of interesti
 
 ### ILogger
 
-For most cases, whether adding logging to an existing project or creating a new project, the [ILogger infrastructure](../extensions/logging.md) is a good default choice. `ILogger` supports fast [structured logging](#structured-and-unstructured-logging), flexible configuration, and a collection of [common sinks](../extensions/logging-providers.md#built-in-logging-providers) including the console, which is what you see when running an ASP.NET app. Additionally, the `ILogger` interface can also serve as a facade over many [third party logging implementations](../extensions/logging-providers.md#third-party-logging-providers) that offer rich functionality and extensibility.
+For most cases, whether adding logging to an existing project or creating a new project, the [ILogger infrastructure](../extensions/logging/overview.md) is a good default choice. `ILogger` supports fast [structured logging](#structured-and-unstructured-logging), flexible configuration, and a collection of [common sinks](../extensions/logging/providers.md#built-in-logging-providers) including the console, which is what you see when running an ASP.NET app. Additionally, the `ILogger` interface can also serve as a facade over many [third party logging implementations](../extensions/logging/providers.md#third-party-logging-providers) that offer rich functionality and extensibility.
 
 ILogger provides the logging story for the OpenTelemetry implementation for .NET, which enables egress of logs from your application to a variety of APM systems for further analysis.
 

docs/core/diagnostics/metrics-strongly-typed.md

@@ -120,4 +120,4 @@ Adhering to these requirements ensures that the source generator can successfull
 - [Source generated metrics in .NET](metrics-generator.md)
 - [Creating metrics in .NET (Instrumentation tutorial)](metrics-instrumentation.md)
 - [Collecting metrics in .NET (Using MeterListener and exporters)](metrics-collection.md)
-- [Logging source generation in .NET](../extensions/logger-message-generator.md) (for a similar source-generation approach applied to logging)
+- [Compile-time logging source generation](../extensions/logging/source-generation.md) (for a similar source-generation approach applied to logging)

docs/core/diagnostics/observability-otlp-example.md

@@ -115,7 +115,7 @@ Each time you request the page, it increments the count for the number of greeti
 
 ### 8.1 Log output
 
-The logging statements from the code are output using `ILogger`. By default, the [Console Provider](../extensions/logging.md?tabs=command-line#configure-logging) is enabled so that output is directed to the console.
+The logging statements from the code are output using `ILogger`. By default, the [Console Provider](../extensions/logging/overview.md?tabs=command-line#configure-logging) is enabled so that output is directed to the console.
 
 There are a few options for how logs can be egressed from .NET:
 

docs/core/diagnostics/observability-prgrja-example.md

@@ -68,7 +68,7 @@ Each time you request the page, it increments the count for the number of greeti
 
 ### 6.1 Log output
 
-The logging statements from the code are output using `ILogger`. By default, the [Console Provider](../extensions/logging.md?tabs=command-line#configure-logging) is enabled so that output is directed to the console.
+The logging statements from the code are output using `ILogger`. By default, the [Console Provider](../extensions/logging/overview.md?tabs=command-line#configure-logging) is enabled so that output is directed to the console.
 
 There are a few options for how logs can be egressed from .NET:
 

docs/core/diagnostics/observability-with-otel.md

@@ -18,7 +18,7 @@ Observability in the context of a distributed system is the ability to monitor a
 
 Observability is commonly done using a combination of:
 
-- [Logs](../extensions/logging.md), which record individual operations, such as an incoming request, a failure in a specific component, or an order being placed.
+- [Logs](../extensions/logging/overview.md), which record individual operations, such as an incoming request, a failure in a specific component, or an order being placed.
 - [Metrics](./metrics.md), which are measuring counters and gauges such as number of completed requests, active requests, widgets that have been sold; or a histogram of the request latency.
 - [Distributed tracing](./distributed-tracing.md), which tracks requests and activities across components in a distributed system so that you can see where time is spent and track down specific failures.
 
@@ -56,7 +56,7 @@ There are OpenTelemetry implementations for most languages and platforms, includ
 
 The .NET OpenTelemetry implementation is a little different from other platforms, as .NET provides logging, metrics, and activity APIs in the framework. That means OTel doesn't need to provide APIs for library authors to use. The .NET OTel implementation uses these platform APIs for instrumentation:
 
-- <xref:Microsoft.Extensions.Logging.ILogger%601?displayProperty=nameWithType> for [logging](../extensions/logging.md)
+- <xref:Microsoft.Extensions.Logging.ILogger%601?displayProperty=nameWithType> for [logging](../extensions/logging/overview.md)
 - <xref:System.Diagnostics.Metrics.Meter?displayProperty=nameWithType> for [metrics](./metrics-instrumentation.md)
 - <xref:System.Diagnostics.ActivitySource?displayProperty=nameWithType> and
 <xref:System.Diagnostics.Activity?displayProperty=nameWithType> for [distributed tracing](./distributed-tracing.md)

docs/core/extensions/generic-host.md

@@ -321,7 +321,7 @@ To ensure a smooth transition of clients to a new destination when working with
 ## See also
 
 - [Dependency injection in .NET](dependency-injection/overview.md)
-- [Logging in .NET](logging.md)
+- [Logging in .NET](logging/overview.md)
 - [Configuration in .NET](configuration.md)
 - [Worker Services in .NET](workers.md)
 - [ASP.NET Core Web Host](/aspnet/core/fundamentals/host/web-host)