Page MenuHomePhabricator

Investigate bad_token statsd spikes
Closed, DeclinedPublic

Description

http://graphite.wikimedia.org/render/?width=887&height=556&_salt=1440105991.976&from=-4weeks&target=divideSeries(MediaWiki.edit.failures.bad_token.count,MediaWiki.site.edits.count)&lineMode=connected&drawNullAsZero=false

This metric has been spikey, with waves of activity for it's lifetime. It's not immediately obvious why we'd get bad token errors in these patterns.

Event Timeline

aaron raised the priority of this task from to Needs Triage.
aaron updated the task description. (Show Details)
aaron subscribed.
Krinkle closed this task as Declined.EditedDec 3 2016, 6:43 AM

<http://graphite.wikimedia.org/render/?width=887&height=556&from=-4weeks&target=divideSeries(MediaWiki.edit.failures.bad_token.count,MediaWiki.site.edits.count)&lineMode=connected&drawNullAsZero=false

The .count properties represent the number of packets received by statsd, not their value. So in a minute that saw three +0 values, three +1, three +10, all get recorded as a 3 in count.

Data from August 2015 appears to no longer be in Graphte for these properties for some reason (only goes back to December 2015).

More recent query:

Screen Shot 2016-12-02 at 22.39.23.png (496×1 px, 81 KB)

And at https://grafana.wikimedia.org/dashboard/db/edit-count:

Screen Shot 2016-12-02 at 22.45.12.png (898×2 px, 323 KB)

Closing for now as bad_token is fairly rare.