Page MenuHomePhabricator

Make Search Platform metrics available in Druid
Open, NormalPublic

Description

Metrics:

  • search satisfaction (# clicks & # impressions, then compute clickthrough rate as a post-aggregation)
  • results page load times
  • overall volume (# searches)
  • zero results rate (# zero results searches, compute as a post-aggregation using # searches)
  • API volume (# API requests)

Dimensions:

  • language & language code
  • project & project code
  • platform (desktop/mobile web/iOS/Android)
  • search type (full-text, “Go” box, morelike, autocomplete searches)

These will be available, initially, as a test_search_platform data cube and then later renamed to search_platform.

Event Timeline

mpopov triaged this task as Normal priority.Jul 11 2019, 2:36 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.
mpopov updated the task description. (Show Details)Jul 11 2019, 3:30 PM
TJones added a subscriber: TJones.Jul 15 2019, 5:12 PM

Things that show up as important in our metric-rating spreadsheet that do not seem to be covered by the current list include:

Metrics

  • abandoned sessions (i.e., no click on search results)
  • expert syntax usage (i.e., using keywords or wildcards)

However, we don't have either of these at the moment, so they aren't critical for a first-pass MVP.

notes for future self:

  • abandoned sessions can just be a post-aggregation metric impressions - clicks, doesn't have to be present at ingestion time
  • expert syntax usage would have to be a boolean dimension, not a metric. we can then compare volumes of searches between true and false values of this dimension