You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: aspnetcore/fundamentals/logging/index.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -186,7 +186,7 @@ The following table lists the <xref:Microsoft.Extensions.Logging.LogLevel> value
186
186
|[Warning](xref:Microsoft.Extensions.Logging.LogLevel)| 3 |[LogWarning](/dotnet/api/microsoft.extensions.logging.loggerextensions.logwarning)| For abnormal or unexpected events. Typically includes errors or conditions that don't cause the app to fail. |
187
187
|[Error](xref:Microsoft.Extensions.Logging.LogLevel)| 4 |[LogError](/dotnet/api/microsoft.extensions.logging.loggerextensions.logerror)| For errors and exceptions that cannot be handled. These messages indicate a failure in the current operation or request, not an app-wide failure. |
188
188
|[Critical](xref:Microsoft.Extensions.Logging.LogLevel)| 5|[LogCritical](/dotnet/api/microsoft.extensions.logging.loggerextensions.logcritical)| For failures that require immediate attention. Examples: data loss scenarios, out of disk space. |
189
-
|[None](xref:Microsoft.Extensions.Logging.None)| 6|| Specifies that a logging category should not write any messages. |
189
+
|[`None`| 6|| Specifies that a logging category should not write any messages. |
190
190
191
191
In the previous table, the `LogLevel` is listed from lowest to highest severity.
0 commit comments