Skip to content

Enhance LogLevel docs - #37587

Closed
Youssef1313 wants to merge 1 commit into
mainfrom
dev/ygerges/loglevel
Closed

Enhance LogLevel docs#37587
Youssef1313 wants to merge 1 commit into
mainfrom
dev/ygerges/loglevel

Conversation

@Youssef1313

@Youssef1313 Youssef1313 commented Sep 4, 2026

Copy link
Copy Markdown
Member

<xref:Microsoft.Extensions.Logging.LogLevel.Trace> | 0 | <xref:Microsoft.Extensions.Logging.LoggerExtensions.LogTrace%2A> | Contain the most detailed messages. These messages may contain sensitive app data. These messages are disabled by default and should ***not*** be enabled in production.
<xref:Microsoft.Extensions.Logging.LogLevel.Debug> | 1 | <xref:Microsoft.Extensions.Logging.LoggerExtensions.LogDebug%2A> | For debugging and development. Use with caution in production due to the high volume of messages logged.
<xref:Microsoft.Extensions.Logging.LogLevel.Trace> | 0 | <xref:Microsoft.Extensions.Logging.LoggerExtensions.LogTrace%2A> | Contain the most detailed messages. These messages may contain sensitive app data. These messages are disabled by default and must ***not*** be enabled in production.
<xref:Microsoft.Extensions.Logging.LogLevel.Debug> | 1 | <xref:Microsoft.Extensions.Logging.LoggerExtensions.LogDebug%2A> | For debugging and development. These must **not** be enabled in production.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Have to disagree with the wording. I think previous phrasing is perfect - it tells to be cautious but in case of emergency or deep investigations it may be necessary to turn on debug logging.

What is the reasoning for the PR at all?

@Youssef1313 Youssef1313 closed this Sep 4, 2026
@Youssef1313
Youssef1313 deleted the dev/ygerges/loglevel branch September 4, 2026 10:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants