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.
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