Closed
Bug 1311288
Opened 9 years ago
Closed 9 years ago
ATMO V2: Enable Sentry error reporting
Categories
(Cloud Services Graveyard :: Metrics: Pipeline, defect)
Cloud Services Graveyard
Metrics: Pipeline
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jezdez, Assigned: jezdez)
References
Details
Attachments
(1 file)
New Relic is awesome for application monitoring but lacks the exception details used when debugging errors. We should add Mozilla's own Sentry instance to ATMO to be able to see what's going on.
Assignee | ||
Comment 1•9 years ago
|
||
Hey Blake, is there anything you can do to help us set up a project in Sentry? I'm happy to hook up the code in ATMO itself if you want.
Flags: needinfo?(bimsland)
Comment 2•9 years ago
|
||
If you'd be up for setting up the code that'd be awesome. I made a team and a project in our sentry install (which it looks like you already had an account for) and added you to it. If you go to the "Settings" page of the "ATMO / dev" project in Sentry there are links on the left under "Setup" for "Instructions" and "Client Keys (DSN)" which should give you everything you need.
Flags: needinfo?(bimsland)
Assignee | ||
Updated•9 years ago
|
Assignee: nobody → jezdez
Status: NEW → ASSIGNED
Assignee | ||
Comment 3•9 years ago
|
||
:robotblake Thank you!
Comment 4•9 years ago
|
||
Assignee | ||
Comment 5•9 years ago
|
||
Adding bug 1311634 since there are some questions to Blake about it
Depends on: 1311634
Assignee | ||
Updated•9 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Updated•7 years ago
|
Product: Cloud Services → Cloud Services Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•