1490830 - Please set up Sentry for Firefox Monitor

Status: RESOLVED FIXED

(Cloud Services :: Operations: Deployment Requests - DEPRECATED, task)

Description

[Luke Crouch [:groovecoder]]

We would like to have Sentry monitoring for https://monitor.firefox.com and https://blurts-server.stage.mozaws.net/

If possible, we would also like to log client-side browser errors into Sentry using the official Raven.js client:

https://docs.sentry.io/clients/javascript/

For that, the docs say we will need the <key> and <project> to pass to this code:

Raven.config('https://<key>@sentry.io/<project>').install()

Comment 1

[Bob Micheletto [:bobm]]

This is still something we should do.  If you add ENVs for this, I can create the project and add the key and such to our configuration.

Comment 2

[Luke Crouch [:groovecoder]]

I filed https://bugzilla.mozilla.org/show_bug.cgi?id=1503396 in the Sentry component.

Comment 3

[Jeremy Orem [:oremj]]

This should go to our sentry instance. https://sentry.prod.mozaws.net

Comment 4

[Luke Crouch [:groovecoder]]

I don't have permissions to create a new project in https://sentry.prod.mozaws.net/operations/ for Monitor. Does someone else do that? Or can I get access?

Comment 5

[Bob Micheletto [:bobm]]

(In reply to Luke Crouch [:groovecoder] from comment #4)
> I don't have permissions to create a new project in
> https://sentry.prod.mozaws.net/operations/ for Monitor. Does someone else do
> that? Or can I get access?

I will create one.

Comment 6

[Luke Crouch [:groovecoder]]

I got errors to send into https://sentry.prod.mozaws.net/operations/firefox-monitor-prod/ from my local dev box.

I'm sending the NODE_ENV value in "environment" property while capturing errors, so - to be extra pedantic - can we rename the project to just "firefox-monitor" and use the filter(s) to filter events by environment?

Comment 7

[Bob Micheletto [:bobm]]

(In reply to Luke Crouch [:groovecoder] from comment #6)
It has been renamed to just "firefox-monitor".

Comment 8

[Luke Crouch [:groovecoder]]

I see events coming from the heroku environment and they are correctly tagged as such.

I'm leaving this open to remind us to verify this in stage & prod too.

Comment 9

[Bob Micheletto [:bobm]]

(In reply to Luke Crouch [:groovecoder] from comment #8)
How do you want to handle the configuration for this?  I suggest adding a new ENV for the Sentry DSN.

Comment 10

[Luke Crouch [:groovecoder]]

Yup, it's set up via an env var. https://bugzilla.mozilla.org/show_bug.cgi?id=1505610 has the env var for deploy and where to get the key.

We can close this now that we have sentry set up and we just need to deploy v3.0.0 to activate it on stage & then prod.