Page MenuHomePhabricator

Wikipedia.org Portal Dashboard: Investigate spike in actions taken on the page
Closed, ResolvedPublic

Description

Please investigate what might have happened on June 17th, 18th and 19th that caused a huge spike in the numbers reported for the 'no action' and 'search' results that are showing on the dashboard, as the numbers have not yet returned to 'normal' since.

Screen Shot 2016-06-30 at 10.28.41 PM.png (669×1 px, 155 KB)

Screen Shot 2016-06-30 at 10.28.08 PM.png (680×1 px, 155 KB)

Event Timeline

debt triaged this task as High priority.Jun 30 2016, 8:35 PM

Change 299085 had a related patch set uploaded (by Bearloga):
Revert commit from 20 June 2016

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

Change 299085 merged by Bearloga:
Revert commit from 20 June 2016

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

Reverted & backfilled:

Screen Shot 2016-07-14 at 3.38.24 PM.png (478×1 px, 111 KB)

Report coming soon.

debt reopened this task as Open.
debt claimed this task.

oops - closed too soon, we're still waiting on the report.

One question on wording: "...snaply determined as..." in the first paragraph. Not sure that what means.

Also - are there any recommendations to how better get this data within our normal guidelines?

Thanks!

One question on wording: "...snaply determined as..." in the first paragraph. Not sure that what means.

I wasn't sure how else to succinctly summarize "Well, I was looking at the code and that line stood out to me as unnecessary after all the discussions we've had about clickthrough rates and how they should be calculated, so I made a snap judgement to get rid of that line because it seemed counter to how we decided that metric should be calculated."

Also - are there any recommendations to how better get this data within our normal guidelines?

Could you please elaborate on what you mean?

LOL, fair enough. ;)

I was wondering which one of these options you wanted to try / go with, based on your analysis without having to do more logging of our visitor's actions/tracking:

"We conclude with a proposal of an alternative metric, either the “most commonly clicked section per visit” or “most common section clicked on across all visits per session”."

Also....the pageviews also has a spike during this same timeframe - is that ok or does it need to be adjusted?

I was wondering which one of these options you wanted to try / go with, based on your analysis without having to do more logging of our visitor's actions/tracking:

"We conclude with a proposal of an alternative metric, either the “most commonly clicked section per visit” or “most common section clicked on across all visits per session”."

It looks like the second one follows the original metric really closely, if not perfectly. The "most commonly clicked section per visit" metric is at least different enough. Hm.

Also....the pageviews also has a spike during this same timeframe - is that ok or does it need to be adjusted?

That one is completely independent and even excludes search-redirect.php! :D