Page MenuHomePhabricator

Create a Superset dashboard for Nearby metrics
Open, Needs TriagePublic8 Estimated Story Points

Description

  • Get the new event stream wired into superset data sets. The default is that event streams are not available. I believe that wiring a stream involves editing this puppet module.
  • Panel: Number of opens of fullscreen map
  • Panel: Number of first clicks (= only once per fullscreen session) on the nearby button, as a percentage of fullscreen views.
  • Panel: Number of first clicks (= only once per nearby session) on nearby pop-up article links, as a percentage of nearby sessions.
  • Segment graphs by wikipedia vs wikivoyage
  • (Nice-to-have) Allow segmentation by individual wiki

Implementation

Superset dashboard: Maps interactions: "nearby" feature

Event Timeline

awight set the point value for this task to 8.Sep 29 2022, 1:00 PM
This comment was removed by Andrew-WMDE.

Some review notes, (and one thing I fixed during review, just recorded here)

  • Interesting that there was no puppet patch needed! Do these new-fangled event streams show up in Superset by default?
  • 4 days is a good time window for this draft, but the main use case seems to be historical rather than operational, so maybe the default should be a 1-month window, or...? Also, the time range needs to be relative, eg. "last 4 days".
  • For these percentage graphs, I agree with anchoring y-min at 0, but it seems that the y-max should automatically fit the values.
  • "Map image requests table" has no data. It's filtering to one hour in history, on 2021-11-01. webrequest is purged after 90 days, so I don't see how this would have worked. Also, shouldn't the time window be relative, ie. "in the past 4 days"? On a side note, I'm curious about how often this data source is evaluated. Is it one-off, or designed for relative times and then somehow cached for eg. one day?
  • I think the filter should be reworked to target specific wikis rather than separate language and project. We never need to segment by "all German-language wikis", it's more like "show German Wikipedia and English Wikivoyage".
  • 4 days is a good time window for this draft, but the main use case seems to be historical rather than operational, so maybe the default should be a 1-month window, or...? Also, the time range needs to be relative, eg. "last 4 days".

It now defaults to the last month

  • "Map image requests table" has no data. It's filtering to one hour in history, on 2021-11-01. webrequest is purged after 90 days, so I don't see how this would have worked. Also, shouldn't the time window be relative, ie. "in the past 4 days"? On a side note, I'm curious about how often this data source is evaluated. Is it one-off, or designed for relative times and then somehow cached for eg. one day?

This chart was already broken long before I picked this up. I removed it since it doesn't look like anyone was using it.

  • I think the filter should be reworked to target specific wikis rather than separate language and project. We never need to segment by "all German-language wikis", it's more like "show German Wikipedia and English Wikivoyage".

Done

awight moved this task from Tech Review to Demo on the WMDE-TechWish-Sprint-2022-10-26 board.

Really nice showcase of our new metrics pipeline!