reduce verbosity level #823
Merged
Conversation
This file contains 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
Signed-off-by: hanenMizouni <[email protected]>
Signed-off-by: hanenMizouni <[email protected]>
outscale-toa
approved these changes
Oct 8, 2024
Closed
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.
Is this a bug fix or adding new feature?
it is a configuration change aimed at improving logging behavior.
What is this PR about? / Why do we need it?
This PR reduces the logging verbosity level in the CSI driver from 10 to 3. The previous verbosity level generated an excessive amount of log output, which made it challenging to identify critical information and errors during troubleshooting.
Verbosity Levels explanation:
0: Fatal errors that prevent the application from continuing.
1: Errors that occur during execution but allow the application to continue.
2: Warnings that indicate potential issues but do not stop execution.
3: Informational messages that provide insight into the normal operation.
4: Debugging information that might be useful for development.
5: More detailed debug information.
6-9: Very detailed debug logs, generally not recommended for production use.
10: Extremely verbose debugging information, usually reserved for deep debugging sessions.
What testing is done?