re-add support for Sentry exception tracking

RESOLVED FIXED

Status

Release Engineering
Balrog: Backend
RESOLVED FIXED
8 months ago
7 months ago

People

(Reporter: bhearsum, Assigned: vjoshi)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [lang=python][good first bug])

(Reporter)

Description

8 months ago
I was talking with Benson today about propagating exceptions from Balrog. He mentioned that they have a Sentry instance and we can just send them there. This was working well for us before we switched to New Relic, so I don't see any reason not re-add support. It was previously ripped out in https://bugzilla.mozilla.org/page.cgi?id=splinter.html&bug=1163235&attachment=8610611, so we can probably re-use some of that code.

CloudOps will control which URL is used, so we just need to make sure we look for it in the environment, and pass it along to the plugin.
(Reporter)

Updated

7 months ago
Assignee: nobody → varunj.1011

Comment 1

7 months ago
Commit pushed to master at https://github.com/mozilla/balrog

https://github.com/mozilla/balrog/commit/662e8711623df5cf9efbc7c5642707d8b906ecd1
bug 1302838: Reinstated Sentry logging (#144). r=bhearsum
(Reporter)

Updated

7 months ago
Depends on: 1311036
(Reporter)

Comment 2

7 months ago
This is working in prod. For those that have access, exceptions can be viewed at https://sentry.prod.mozaws.net/.

Thanks for re-adding support for it, Varun!
Status: NEW → RESOLVED
Last Resolved: 7 months ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.