Page MenuHomePhabricator

Integrate Sentry with beta cluster
Closed, DeclinedPublic


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.

Event Timeline

Tgr raised the priority of this task from to Needs Triage.
Tgr updated the task description. (Show Details)
Tgr added a subscriber: Tgr.
Tgr triaged this task as Medium priority.Jul 25 2015, 12:04 AM
Tgr moved this task from Backlog to Goals on the Sentry board.
Tgr set Security to None.
mmodell raised the priority of this task from Medium to Needs Triage.Jul 27 2015, 7:33 PM
mmodell triaged this task as Medium priority.
mmodell moved this task from To Triage to Backlog on the Beta-Cluster-Infrastructure board.
mmodell added a subscriber: mmodell.

I'm guessing this is something to do with the 403s I see in the JS console network tab on beta?

image.png (275×1 px, 62 KB)

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.

Change 399680 had a related patch set uploaded (by Addshore; owner: Addshore):
[operations/mediawiki-config@master] BETA: unset $wgSentryDsn

Change 399680 abandoned by Addshore:
BETA: set wmgSentryDsn to null