As a first step towards deploying Sentry to production, create a deployment-sentry machine which collects JS errors directly and backend errors via Logstash from the beta cluster.
|Open||None||T106915 Use Sentry in production|
|Declined||None||T106920 Integrate Sentry with beta cluster|
|Resolved||Tgr||T84956 Create basic puppet role for Sentry|
|Open||None||T96054 Puppet resource for creating a postgresql database|
|Resolved||jcrespo||T112228 Need to run postgresql::user twice to set the password|
|Open||Tgr||T85239 Channel PHP errors from Logstash to Sentry on the beta cluster|
|Open||None||T97133 Login integration for Sentry|
|Open||None||T97136 Phabricator integration for Sentry|
Probably the Sentry config (specifically the API key) got reset during some maintenance of Cloud VPS boxes. I don't have the time to fix it right now; it should be harmless but if it's getting in the way you can get rid of it by unsetting $wgSentryDsn.