Page MenuHomePhabricator

Add JS error counts to graphite
Open, NormalPublic

Description

In the post-processing step (logstash?) identify where the error comes from at a high level (such as extension name or ResourceLoader module name) and ping graphite so it can show error frequency graphs for those error sources.

For reference, here is how NavigationTiming adds its numbers to graphite: puppet manifest, upstart script, python script

Event Timeline

Tgr created this task.Oct 1 2014, 11:41 AM
Tgr updated the task description. (Show Details)
Tgr raised the priority of this task from to Normal.
Tgr claimed this task.
Tgr changed Security from none to None.
Tgr added a subscriber: Tgr.
Tgr updated the task description. (Show Details)Oct 1 2014, 11:44 AM
Tgr updated the task description. (Show Details)Oct 1 2014, 11:52 AM
Krinkle updated the task description. (Show Details)Dec 12 2014, 11:45 PM
Tgr removed Tgr as the assignee of this task.Jan 30 2015, 2:38 AM
Jdforrester-WMF moved this task from Untriaged to Backlog on the Multimedia board.Sep 4 2015, 6:41 PM
Restricted Application added subscribers: Matanya, Aklapper. · View Herald TranscriptSep 4 2015, 6:41 PM

This has been resolved for Minerva/MobileFrontend (T202026).

We could probably generalise that by moving the simple mw.track -> statsv counter to WikimediaEvents instead so that we have it for other skins/desktop as well, possibly fragmented by skin id.

But, I don't know if this is something we want to further invest in, given work has now started on using EventGate and Logstash for full error indexing (T217142) which would make this obsolete.