Development: Persist structured logs about unexpected errors #248
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
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.
At the moment information about failed HTTP requests and stacktraces of unexpected exceptions on failed command line action invocations are only logged into the main logfile. This file also contains a lot of unrelated information, which can be seen as unimportant noise for anyone not directly related to this package. As such it is difficult for package clients to find out the actual root cause of the failure.
In order to make it easier to include relevant information with bug reports, log error and failure information also separately in a JSON serialized standalone files that are easy to share.
Failed HTTP requests are stored in
and unexpected exceptions are saved in