1302838 - re-add support for Sentry exception tracking

Status: RESOLVED FIXED

(Release Engineering Graveyard :: Applications: Balrog (backend), defect)

Description

[[e-mail] (:bhearsum)]

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.

Comment 1

[[github robot]]

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

Comment 2

[[e-mail] (:bhearsum)]

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!