From 6d5211229e0281add29bdd9b9c5594c3ef565843 Mon Sep 17 00:00:00 2001 From: Pawel Kadluczka Date: Fri, 20 May 2016 13:52:22 -0700 Subject: [PATCH] Update logging.rst --- aspnet/fundamentals/logging.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/aspnet/fundamentals/logging.rst b/aspnet/fundamentals/logging.rst index 9eecef305d..8b748efaf6 100644 --- a/aspnet/fundamentals/logging.rst +++ b/aspnet/fundamentals/logging.rst @@ -78,7 +78,7 @@ Error An error should be logged when the current flow of the application must stop due to some failure, such as an exception that cannot be handled or recovered from. These messages should indicate a failure in the current activity or operation (such as the current HTTP request), not an application-wide failure. Example: ``Cannot insert record due to duplicate key violation`` Critical - A critical log level should be reserved for unrecoverable application or system crashes, or catastrophic failure that requires immediate attention. Examples: data loss scenarios, stack overflows, out of disk space + A critical log level should be reserved for unrecoverable application or system crashes, or catastrophic failure that requires immediate attention. Examples: data loss scenarios, out of disk space The ``Logging`` package provides `helper extension methods `_ for each of these standard ``LogLevel`` values, allowing you to call ``LogInformation`` rather than the more verbose Log(LogLevel.Information, ...) method. Each of the ``LogLevel``-specific extension methods has several overloads, allowing you to pass in some or all of the following parameters: