Skip to content

Commit f1ccfab

Browse files
Fixing table in the README (#6852)
1 parent be8cf03 commit f1ccfab

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

sdk/core/azure-core/README.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -79,12 +79,12 @@ Three main ways of troubleshooting failures are:
7979
### SDK Log Messages
8080

8181
The simplest way to enable logs is to set `AZURE_LOG_LEVEL` environment variable to one of the values:
82-
|`AZURE_LOG_LEVEL`|`Azure::Core::Diagnostics::Logger::Level`|Log message level
83-
|-|-|-
84-
|`4`, or `error`, or `err`|`Error`|Logging level for failures that the application is unlikely to recover from.
85-
|`3`, or `warning`, or `warn`|`Warning`|Logging level when a function fails to perform its intended task.
86-
|`2`, or `informational`, or `information`, or `info`|`Informational`|Logging level when a function operates normally.
87-
|`1`, or `verbose`, or `debug`|`Verbose`|Logging level for detailed troubleshooting scenarios.
82+
|`AZURE_LOG_LEVEL`|`Azure::Core::Diagnostics::Logger::Level`|Log message level|
83+
|-|-|-|
84+
|`4`, or `error`, or `err`|`Error`|Logging level for failures that the application is unlikely to recover from.|
85+
|`3`, or `warning`, or `warn`|`Warning`|Logging level when a function fails to perform its intended task.|
86+
|`2`, or `informational`, or `information`, or `info`|`Informational`|Logging level when a function operates normally.|
87+
|`1`, or `verbose`, or `debug`|`Verbose`|Logging level for detailed troubleshooting scenarios.|
8888

8989
Then, log messages will be printed to console (`stderr`).
9090
Note that `stderr` messages can be redirected into a log file like this:

0 commit comments

Comments
 (0)