Page MenuHomePhabricator

Retire obsolete Discovery Dashboards
Open, LowPublic0 Story Points

Description

With key Search Platform metrics moving to Superset/Turnilo (T227781), we should evaluate the various Discovery Dashboards to reduce maintenance cost & effort if they are not being actively used to drive decision-making.

Retire

  • Wikipedia.org Portal
  • Search Metrics (when ready)
  • Wikimedia Maps (when ready)

Keep (if any)

  • ???

To Be Determined

  • Wikidata Query Service
  • External Referrers

Event Timeline

mpopov triaged this task as Low priority.Jul 11 2019, 2:50 PM
mpopov created this task.
mpopov moved this task from Triage to Backlog on the Product-Analytics board.
mpopov moved this task from needs triage to Tests & Analysis on the Discovery-Search board.

Okay, we've got 3 dashboards to decide fates for:

WDQS

@Smalyshev: Do you use https://discovery.wmflabs.org/wdqs/ for monitoring usage or decision-making?

Maps

@MSantos: You're the closest person to a https://discovery.wmflabs.org/maps/ stakeholder I could find who recently referred to the tile usage dashboard.

  • Will you need that data in FY19-20?
  • For trends and performance analysis, would it be helpful to have a tile usage breakdown by language+project vs non-Wikimedia usage?
    • Once I show you how to query the web logs to find which external websites and apps use our tile servers, will a dashboard like that be relevant?
  • Do you ever care about tile usage broken down by styles and zoom levels?

External traffic

@JKatzWMF / @kzimmerman: This dashboard made sense before we had Superset/Turnilo, but now it's mostly obsolete. The only information we get on this dashboard that we don't have anywhere else is the breakdown of traffic by search engine (https://discovery.wmflabs.org/external/#traffic_by_engine), since the pageview data cube in Druid lumps all of it under the "external (search engine)" referer class.

But since almost all of the search engine traffic is just Google anyway and individual search engine traffic patterns aren't interesting, do we need this additional granularity?

@mpopov

  • Will you need that data in FY19-20?

Yes, this data is important to us in order to push forward some decision making.

  • For trends and performance analysis, would it be helpful to have a tile usage breakdown by language+project vs non-Wikimedia usage?

Yes, it would. This can help us scale hardware and even restrict some access like we had to do with the Pokemon GO issue a few years ago.

  • Once I show you how to query the web logs to find which external websites and apps use our tile servers, will a dashboard like that be relevant?

Yes

  • Do you ever care about tile usage broken down by styles and zoom levels?

No.