[release/0.8] Support specifying a specific logrus log level for shim log output#1213
Merged
dcantah merged 1 commit intomicrosoft:release/0.8from Nov 1, 2021
Merged
Conversation
Sometimes debug is a bit too noisy and can cause log rotation at a higher than ideal rate. This will be accompanied by an audit of our use of log levels throughout to make sure they actually fit what level they're under. Signed-off-by: Daniel Canter <dcanter@microsoft.com> (cherry picked from commit a2d897c) Signed-off-by: Daniel Canter <dcanter@microsoft.com>
Contributor
Author
|
Realized this was never pulled into the release/0.8 branches. Would be nice to have for a new ctrd 1.5 release, and helps with the merge conflicts from just trying to cherry-pick #1197 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Sometimes debug is a bit too noisy and can cause log rotation at a higher than
ideal rate.
This will be accompanied by an audit of our use of log levels throughout to make sure
they actually fit what level they're under.
Signed-off-by: Daniel Canter dcanter@microsoft.com
(cherry picked from commit a2d897c)
Signed-off-by: Daniel Canter dcanter@microsoft.com