Closed
Bug 1439368
Opened 7 years ago
Closed 5 years ago
Set up monitoring of production JS exceptions
Categories
(Tree Management :: Treeherder: Infrastructure, enhancement, P3)
Tree Management
Treeherder: Infrastructure
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1570110
People
(Reporter: emorley, Unassigned)
References
Details
At the moment we have zero monitoring of JS exceptions - and also no way to track custom events (such as would have been useful in bug 1437824).
We should investigate using New Relic browser monitoring or else something like Rollbar/Sentry/Airbrake/Raygun.
Ideally whatever solution we pick would:
* have a NPM package so we don't have to either vendor the JS snippet in our repo or else pull in scripts from third-party domains
* support both exceptions and custom events/annotations
* support sourcemaps natively
Heroku has a number of related addons:
https://elements.heroku.com/addons/
...though we could also consider using standalone accounts for services that don't exist (or are too expensive) on Heroku.
The Taskcluster team apparently use Sentry at the moment, though have mixed comments about it. Eli mentioned wanting to possibly try out Rollbar.
Comment 2•5 years ago
|
||
Tracking it in bug 1570110.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•