Improve log messages from ReportingService
#255
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
When using just `ex.getMessage()` the error message would look like: "Unable to obtain <truncated> due to: foo.bar" Without the exception's class name it's hard to know the real error. Now it looks like: "Unable to obtain <truncated> due to: java.net.UnknownHostException: foo.bar"
d738f2f to
9b9730a
Compare
akodali18
approved these changes
Feb 7, 2023
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.
When using just
ex.getMessage()the error message would look like:Without the exception's class name it can be hard to know the real error. Now it looks like:
Also, some small improvements to the Main.java demo so not include the deprecated WavefrontSenders.