@W-21199400:adding-log-levels#284
Open
shardulnegi-boop wants to merge 1 commit intosalesforce:masterfrom
Open
Conversation
Adding log levels for debug purpose.
|
Thanks for the contribution! It looks like @shardulnegi-boop is an internal user so signing the CLA is not required. However, we need to confirm this. |
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
1 participant
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.
This change introduces explicit log verbosity levels to sloop to mitigate log-flooding issues. Currently, certain events—specifically date/time parsing failures—are being logged at a high frequency. This constant posting to the logs creates significant memory pressure and makes it difficult to monitor actual system health.
By moving these specific logs to LogLevelDebug (V2), we reduce the overhead on the logging subsystem while still allowing for deep troubleshooting when needed.