On Thu, Jan 19, 2017 at 1:35 AM, Federico Leva (Nemo) nemowiki@gmail.com wrote:
AFAIK https://www.mediawiki.org/wiki/Extension:Sentry is the way to go, perhaps currently blocked on procurement (https://phabricator.wikimedia .org/T93138 ).
It's stalled due to lack of time, with a fair amount of puppet wrangling still needed before it could go into production even as a limited experiment.
Also, a lot of its value is conditional on source maps (T47514 https://phabricator.wikimedia.org/T47514) which AFAIK is also stalled due to lack of time.
On Thu, Jan 19, 2017 at 10:58 AM, Bartosz Dziewoński matma.rex@gmail.com wrote:
Using EventLogging mostly works, but it has some strict limitations on the size of data you can record there, so we can't save for example error backtraces. That's still much better than nothing at all, though.
It also wouldn't scale to logging every error on every page, although if you are interested in gadget errors, you could just restrict it to logged-in users.
It would probably be possible to get more intelligent heuristics by moving some of the logic from the Sentry extension to use the EventLogging pipeline (load raven-js on errors, get the stack trace, send the top few rows of it + a hash to EL), to deduplicate browser/language error message differences and detect errors which originate in gadgets. Not sure how far you could get without source maps though.