Unified Telemetry/Status reports/September 4 2015

Unified Telemetry status report September 4, 2015

Last week: Yellow

This week: Yellow -

Data quality, validation
- Client side validation tool being built
- continued focus on v2/v4 executive dashboard roll ups
healthreport content was pushed live; first pass at API changes have been implemented.

Description of Risks/Issues	State	Owner	Plan to Resolve/Mitigation	Target Date
Investigate gaps in pings	Open	Stuart/Alessio	https://bugzilla.mozilla.org/show_bug.cgi?id=1185123, working doc	8/24
Data integrity between V2/V4 and V4 internal data consistency	Open	Brendan/Sam	Investigation in progress. Added resources (Sam). https://etherpad.mozilla.org/fhr-v4-validation	8/24
Data continuity across V2/V4	Open	Katie/Mark/Trink	Plan, Metabug	8/24
Legal review	Open	BDS/Legal	Meeting between groups	8/24
QA sign off (functional, load)	Open	Stuart	Telemetry/Testing	8/24
Operations - data retention requirements	Open	Travis/Katie	Eng team owes ops a doc defining ping types and data retention requirements	8/24
Operations - analysis tools & microservices	Open	Travis/Mark/Roberto	Architecture/Data flow diagram	8/24
Data loss incident	Fixed	mreid/whd/trink	Tee server needs to return error status from old or new. Added Ops resources (Daniel Thornton).	7/15
Remote about:healthreport content	Done	Katie/BDS	Working on pr for fhr-jelly, will deploy next week	8/10
Budget, size of UT pings	Open	Mark/BDS	https://bugzilla.mozilla.org/show_bug.cgi?id=1182693	8/10
Analysis difficulty	Open	Katie/tbd	Spark training; need comprehensive plan	8/10

Description	State	Owner	Plan to Resolve/Mitigation	Target Date
FireFox OS - app pings	Open	Katie	Need to schedule and understand impact on project	TBD
histograms for loop/hello	Open	Katie	Need to schedule and understand impact on project	TBD