Automated Error Reporting #821

Closed
opened 2017-12-06 21:08:01 +01:00 by liamcardenas · 1 comment
liamcardenas commented 2017-12-06 21:08:01 +01:00 (Migrated from github.com)

The Issue

We should log errors to loggly (and maybe amplitude?) and set up some mechanism to notify us / potentially log issues github (probably wouldn't want this) / and provide context for errors to help reproduce them (while preserving privacy).

The first obvious place to do this would be in the error modal. This is more of a brainstorm issue, other any ideas? @kauffj @seanyesmunt @IGassmann @hackrush01 ?

<!-- Thanks for reporting an issue to LBRY and helping us improve! To make it possible for us to help you, please fill out below information carefully. Before reporting any issues, please make sure that you're using the latest version. - App releases: https://github.com/lbryio/lbry-app/releases - Standalone daemon: https://github.com/lbryio/lbry/releases We are also available on live chat at https://chat.lbry.io --> ## The Issue We should log errors to loggly (and maybe amplitude?) and set up some mechanism to notify us / potentially log issues github (probably wouldn't want this) / and provide context for errors to help reproduce them (while preserving privacy). The first obvious place to do this would be in the error modal. This is more of a brainstorm issue, other any ideas? @kauffj @seanyesmunt @IGassmann @hackrush01 ?
tzarebczan commented 2019-05-21 16:32:02 +02:00 (Migrated from github.com)

This has been implemented and logged to Slack.

This has been implemented and logged to Slack.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: LBRYCommunity/lbry-desktop#821
No description provided.