Page MenuHomePhabricator

Track Score errors in statsd and debug logging
Closed, ResolvedPublic

Description

Most Score errors have a unique error code, so we could just send a counter to statsd whenever one is generated. Errors are totally expected from malformed user input, but this can help us track patterns or systemic problems (like T289298). Also sending the page name and revid to debug logging would be nice too.

Event Timeline

Legoktm renamed this task from Track Score errors to Track Score errors in statsd and debug logging.Aug 19 2021, 8:19 PM

Should this be under observability or would that be a stretch?

Change 716004 had a related patch set uploaded (by Legoktm; author: Legoktm):

[mediawiki/extensions/Score@master] Simplify exception creation, track errors in statsd

https://gerrit.wikimedia.org/r/716004

Change 716004 merged by jenkins-bot:

[mediawiki/extensions/Score@master] Simplify exception creation, track errors in statsd

https://gerrit.wikimedia.org/r/716004

Legoktm claimed this task.