Use Sentry to proactively catch errors
Problem
It's not clear which developers should react to Sentry error reports in the Customer Portal. The reports we currently have need to be triaged.
We're also suffering from similar issues mentioned &737
Proposal
Determine a process for handling Sentry errors. Document and codify the process.
Enable relevant alerts for dev team; slack or email.
Concrete TODOs
-
Update Sentry -
Add SentryJS to JS bundle -
Upload sourcemaps to Sentry
How will we measure success?
We're proactive in catching and fixing bugs instead of customers reporting them.
Edited by Ragnar Hardarson