Page MenuHomePhabricator

Identify top mobile error rate contributors
Closed, ResolvedPublic


The mobile site's error rate has steadily climbed to ~30k / minute as we've focused on desktop facing changes. Why do these keep going up? We had hoped to see these reports diminish once T253084 landed but the rate persists. This task tracks the work to investigate the top contributors and create tickets for their resolution.

The mobile site seems to be tracked by the new error logger which includes stack traces.

Acceptance Criteria

  • One new ticket per bug is made.
  • Each new ticket contains a strack trace, the approximate number of occurrences, and the top platforms for reproduction.

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptJun 4 2020, 2:41 PM
Niedzielski updated the task description. (Show Details)Jun 4 2020, 3:06 PM

The mobile site seems to be tracked by the new error logger which includes stack traces.

It only tracks and these errors are not on I looked through the bugs on and there was not enough data to draw conclusions :(

Jdlrobson moved this task from Incoming to Needs Prioritization on the Readers-Web-Backlog board.

Moving to triaged but future for now, but lets keep an eye on it - we can do some analysis later on.

Jdlrobson moved this task from Backlog to Team: web on the MobileFrontend board.Jul 24 2020, 2:36 AM
Jdlrobson closed this task as Resolved.Sep 16 2020, 10:53 PM

This is settling now. The main perpetrator was T255204 which was not so widespread. The error rate was amplified because the errors were repeatedly sent.

T255585: Extend client-side error logging coverage will allow us to detect other ones. It seems the error counter is also picking up a lot of inactionable noise so is much higher than reality.