Last modified: 2014-07-30 09:43:03 UTC
It'd be great if fatals and exceptions were automagically logged into BZ with stack traces. Obviously just logging every occurrence straight into BZ would be a mess. There was talk of a logstash dedupe tool that might help allievate this problem...
Dropping priority. It'd be nice to have, but it really isn't urgent
Suggested tool is https://sentry.readthedocs.org/en/latest/
Obligatory "make sure we don't expose sensitive data" comment.
Related: https://github.com/thurloat/sentry-jira It lets you create JIRA issues from Sentry items/whatever they're called. No Bugzilla plugin yet. But there is a Phabricator plugin: https://github.com/getsentry/sentry-phabricator :) :) So, that would allow manual task creation, not automatic. Maybe good enough for a first step.
A logstash to sentry output plugin (http://clarkdave.net/2014/01/tracking-errors-with-logstash-and-sentry/) may come in handy
Testing instance (un-puppeted POC) at https://sentry-beta.wmflabs.org. The phabricator plugin is installed. We need to 1) get some data in there, 2) setup a phabricator user to post bugz, 3) configure sentry to use the user. For the "no private data" part, maybe we should setup the project that the bugs are posted to as private somehow and let a human triage them?
(In reply to Bryan Davis from comment #6) > For the "no private data" part, maybe we should setup the project that the > bugs are posted to as private somehow and let a human triage them? That's what I was thinking, yeah. We can reuse what Mukunda did for the Security project, but no spam the Security project.
