Note that the format of the data in TSS2 is very different from Search so the switch is non-trivial. This is also an entirely backend change and nothing on the dashboards needs to be changed, except this switch will result in different values for the Desktop data, and should be annotated appropriately.
|wikimedia/discovery/rainbow : master||Annotate Desktop schema switch|
|wikimedia/discovery/golden : master||Switch Desktop data from Schema:Search to Schema:TSS2|
- Mentioned In
- T132516: Add time to display results to logging in Schema:TestSearchSatisfaction2
T130321: Disable Schema:Search, since it's outdated and redundant
- Mentioned Here
- T134319: Turn off TextCat A/B test on the English Wikipedia on or after May 23
T132516: Add time to display results to logging in Schema:TestSearchSatisfaction2
I don't think this is a sufficiently defined task. Which metrics precisely are we meant to surface that we are currently not?
As it is described, I think this is actually a task asking us to switch our Desktop-related metrics from Schema:Search to Schema:AutocompleteSatisfaction? Also it seems like we would benefit from having a second zero results rate on the dashboard that is derived from AutocompleteSatisfaction, rather than Cirrus request logs.
Yes, having thought about it more I guess that is what I'm asking. Let's make this task for that.
Also it seems like we would benefit from having a second zero results rate on the dashboard that is derived from AutocompleteSatisfaction, rather than Cirrus request logs.
That sounds worthwhile, but should be in a separate task for that.
I just realized that there's a component that Schema:Search has that Schema:TestSearchSatisfaction2 doesn't: time to display results, which means we can't switch the data scripts to the new schema because that'd stop the data used for http://discovery.wmflabs.org/metrics/#desktop_load
@EBernhardson: do you think we can add a "time it took to display SERP" field for the action=searchResultPage events? How doable is that?
SELECT min(event_msToDisplayResults) FROM TestSearchSatisfaction2_15700292; gives -1473820578422
So I think we're still stalled on this because there appears to be a bug in calculating time to display results.
Switched to using TestSearchSatisfaction2 instead of Search schema for Desktop event counts and load times data. Let's keep Search up for another week or so just in case something isn't working as it should. Annotations have been deployed to the beta version, but not production: http://discovery-beta.wmflabs.org/metrics/