Background
During the reading list experiment, we created desktop and mobile instrumentation to track usage of the feature. We need to transition them to permanent instrumentation in order to track usage trends as a beta feature.
The experimentation platform team has created some documentation around how to do so, although some of the strings still say "xLab" when it's possible that this needs to be updated to the newest name: test kitchen.
NOTE: this will encompass switching the custom stream we created to the web stream as we can now select custom contextual attributes via the UI with the instrument workflow
Remaining work as I understand it:
- confirm with Jennifer whether the redundant metrics identified in T418289 are sufficient, given discrepancies in sampling/contextual attributes
- follow the above documentation, substituting xlab for test kitchen, on relevant metrics
- switch the custom stream to use web base stream, and decommission the now-unused custom stream
Design requirements
Add design requirements or link to design files.
Requirements
- All events are logged as documented under the "Instrumentation long-term" tab of the instrumentation spec here. This does not include the grayed out sections.
- all events are tracked via the ReadingList instrument and not pulled from other instruments, even with redundancy we want to keep all the tracking together under one instrument.
- remove page_load for init events.
- remove article_count from action_context.
- instrumentation is for all logged in users using reading lists
- the mediawiki.product_metrics.reading_list stream is removed from mediawiki-config
Acceptance criteria
BDD
- For QA engineer to fill out.
Test Steps
- For QA engineer to fill out.
Communication criteria
Add if this needs an announcement or discussion.
Rollback plan
Describe the rollback plan in production for this task if something goes wrong.
This task was created by Version 1.0.0 of the Reader Experience team task template using phabulous.