fix(log): include exception message in CPU stats warning log#3108
Merged
fix(log): include exception message in CPU stats warning log#3108
Conversation
Include e.getMessage() in the warn/debug log output so that the root cause is visible in single-line log consumers such as Slack notifications, without requiring access to the full stack trace.
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.
Summary
Include exception message in the
LoadControlMonitorTargetwarning log so that the root cause is visible in single-line log consumers like Slack notifications.Changes Made
LoadControlMonitorTarget.expired()to embede.getMessage()in the warn/debug log format string{}placeholder renders the exception message inline, while the trailingeargument preserves the full stack trace in log filesBefore
After
Testing
mvn compileAdditional Notes