Unified Telemetry: Difference between revisions

Line 26: Line 26:
** Release population (opt-out) sends telemetry base data
** Release population (opt-out) sends telemetry base data
=== Acceptance Criteria (Beta -> Release) ===
=== Acceptance Criteria (Beta -> Release) ===
* Basic tool support
** Telemetry Dashboard works against new pipeline dwh
** Telemetry-dash (or new equivalent) can launch spark, heka reporting jobs
* metrics team signoff
* metrics team signoff
** metrics team analysis can proceed on new data streams
** longitudinal data has internal consistency and consistency with v2: [https://bugzilla.mozilla.org/show_bug.cgi?id=1169103 Tracking Bug 1169103]
** longitudinal data has internal consistency and consistency with v2: [https://bugzilla.mozilla.org/show_bug.cgi?id=1169103 Tracking Bug 1169103]
** executive dashboard (in particular MAU)
** executive dashboard (in particular MAU)
** search analysis
** search analysis
* pipeline/ops team signoff
* pipeline/ops team signoff
** No hourly rate spikes: [https://bugzilla.mozilla.org/show_bug.cgi?id=1140037 Telemetry submission rate spikes every hour]
** pipeline is ready and can handle capacity
** monitoring and alerting set up
** no blocking issues:
*** [https://bugzilla.mozilla.org/show_bug.cgi?id=1140037 Telemetry submission rate spikes every hour]
* performance team signoff
* performance team signoff
* Basic tool support
** performance team analysis can proceed on new data streams
** Telemetry Dashboard works against new pipeline dwh
** <bug tree here>
** Telemetry-dash (or new equivalent) can launch spark, heka reporting jobs
* qa signoff
** <bug tree here>
* ua signoff
** Doesn't put any burden on the user (prefs are respected, no performance issues, etc.)
** <bug tree here>


= Client work =
= Client work =
Confirmed users
539

edits