-
Notifications
You must be signed in to change notification settings - Fork 9.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[AuthZ] Switch to debug logging to cut down on noise #29137
Conversation
formatString: "Authorization was successful."); | ||
_userAuthorizationFailed = LoggerMessage.Define<string>( | ||
eventId: new EventId(2, "UserAuthorizationFailed"), | ||
logLevel: LogLevel.Information, | ||
logLevel: LogLevel.Debug, | ||
formatString: "Authorization failed. {0}"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The failure scenario seems to be providing more data than they reported in the issue. Looks like that was a 5.0 change?
If the failure case is providing useful details now then we should keep that at the existing log level.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It depends on the code path really, but sure we can keep the failure as Information and the success as Debug, thoughts @blowdart ? There's potentially more information if requirements failed as opposed to explicit Fail being called
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Darn it. Ok yes, keep fail as informational then.
Hello @HaoK! Because this pull request has the p.s. you can customize the way I help with merging this pull request, such as holding this pull request until a specific person approves. Simply @mention me (
|
For #28234