949791 - [amo/mkt/webpay/solitude] use reliable sentry transport

Status: RESOLVED FIXED

(Cloud Services :: Operations: Marketplace, task, P4)

Description

[Kumar McMillan [:kumar]]

If any marketplace/webpay/solitide app is not logging to sentry due to some bug or misconfiguration (see bug 949182) then this would be a catastrophic problem because we rely on sentry for debugging site issues. We need to know immediately if sentry logging breaks so we can fix it.

Let's create a monitoring script (nagios?) that tells us if the apps are connected to sentry or not.

Comment 1

[Andy McKay]

How would we tell if this was working? The only true test I can think of is to send an error from marketplace through to sentry and to see if it shows up in sentry.

Comment 2

[Chuck Harmston [:chuck]]

That seems reasonable; we currently have an API endpoint that returns a 500 if ENABLE_API_ERROR_SERVICE is set to True.

Comment 3

[Andy McKay]

Looks like there might be an API in here: https://github.com/getsentry/sentry/blob/master/src/sentry/web/api.py

Comment 4

[Andy McKay]

Chatting to davidcramer in IRC, he said all those API's require a session cookie. We'd probably have to write something if we wanted an API to call in sentry.

Comment 5

[Jeremy Orem [:oremj]]

We are switching to the HTTP transport. In this case, the app will be able to tell when a traceback submission has failed and should log any occurrences.

Comment 6

[Jeremy Orem [:oremj]]

I've moved production sentry to the HTTP transport.