I’m not totally sure.  statsd doesn’t actually store anything; these metrics are saved by graphite.  We may have to manually purge them.  I’d open a Phab ticket, CC me, and tag Operations.

On Wed, Jan 25, 2017 at 3:34 PM, Sam Smith <samsmith@wikimedia.org> wrote:

How do we go about purging data from statsd? We recently stopped incrementing a handful of keys (see below) that we haven't used in quite some time and would like to tidy up after ourselves.



---------- Forwarded message ----------
From: Sam Smith <samsmith@wikimedia.org>
Date: Wed, Jan 25, 2017 at 8:22 PM
Subject: Removing wfIncrStats from MobileFrontend's Special:MobileOptions page
To: mobile-l <mobile-l@lists.wikimedia.org>, Internal communication for WMF Reading team <reading-wmf@lists.wikimedia.org>


Some time ago, the Reading Web team noticed that the Special:MobileOptions page is instrumented in two distinct ways: using EventLogging and wfIncrStats. We had a little spare bandwidth this sprint and got around to removing the wfIncrStats-based logging from Special:MobileOptions.

As of today's deploy, we won't be incrementing the following keys in statsd:
  • mobile.options.views
  • mobile.options.errors
  • mobile.options.saves
We'll be looking into and documenting other wfIncrStats-based logging in the MobileFrontend codebase soon.



Analytics mailing list