-
Couldn't load subscription status.
- Fork 51
Description
Create a Kermit logger that stores logs, so we can have a breadcrumb trail of what happened. This would just get stored in memory. I don't expect we'll have much to track, so this doesn't need to be very optimized.
Wrap the main function. If anything throws, ask the user if we can report it (y/n), then create a log file with the exception and the breadcrumb trail. We can add a simple POST endpoint to the Faktory API/Spring server and push these into an S3 bucket. I'd suggest chronological naming to make it easy to see by time.
This will only be usable at low traffic, which is what I would expect for quite some time. Eventually we may want to bump this up to a proper crash reporter, which can group crashes by stack trace.
I think we should set debug build to always upload. Release build should ask. Discuss!