We should have public dashboards for UploadWizard's EventLogging data. We log uncaught JS exceptions, raw data about API errors/warnings, and (messy) data about errors shown in the interface.
Right now, I have a set of SQL queries and a LibreOffice spreadsheet to query and chart this data. This is rather inconvenient, and requires you to have access to Analytics slaves to run the queries.
I've posted some of these in the past on T136230, but I don't recall if I've published the others anywhere and they were modified since, so here goes. The queries are a bit crazy, because they massage the data into a format I could directly generate a chart in LibreOffice for (I know SQL better than spreadsheet formulas ;) ). The one for exceptions has hard-coded conditions to exclude some noise from browser extensions etc. – these will need to be updated occasionally. They show stats for the most common 23 entries (it's hard to make a color palette with more unique colors than that), plus an aggregate of all the remaining ones, over the last 35 days. The spreadsheet automatically pulls data from the .tsv files if placed in the same directory. Consider this work to be in the public domain (CC-0, or any license you wish).
| The queries | Example outputs | The spreadsheet |
|---|---|---|
| Example chart |
|---|
 |
I don't know how to even start doing this, and I'm not even technically on the Multimedia team anymore, so I'm making this your problem :) It would be good if someone working on UploadWizard checked the stats every couple of days for big spikes.
A public dashboard for exceptions has to be considered carefully, since occasionally user's private data can leak into them (e.g. T136851). Only showing the most common entries (in this case, 23 most common) over a fairly long time range (in this case, 35 days) should be sufficient to prevent displaying any of that – you'd have to make sure the dashboard doesn't display any finer data. As long as we ensure that, it should be safe to share (I've been using this for a couple months and never noticed anything private in the .tsv files generated by these queries), but it should probably be extra-okayed by Legal.