Unified Telemetry/Status reports/August 14 2015: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 6: Line 6:
Last week: Yellow
Last week: Yellow


This week: Yellow - The primary risk is now the executive report. We're still debugging the discrepancies between the v4 and the v2 versions. We will not turn off v2 data if we don't have confidence in the executive report.
This week: Yellow - Discrepancies in the executive rollups remain a significant risk; if we don't resolve these in the next two week iteration, we can't turn off FHRv4. As a risk mitigation strategy, we've implemented the ability to send v4 data for a 5% sample of v4 clients for the opt-out release population. We have a meeting scheduled on '''Aug 24''' to make the decision, so that we can have everything set to go by Fx41 beta6.
 
August 24th is go/no go meeting.


=== Exec Summary ===
=== Exec Summary ===

Revision as of 20:48, 14 August 2015

previous weeks report

Unified Telemetry status report August 14, 2015

Overall Project Health

Last week: Yellow

This week: Yellow - Discrepancies in the executive rollups remain a significant risk; if we don't resolve these in the next two week iteration, we can't turn off FHRv4. As a risk mitigation strategy, we've implemented the ability to send v4 data for a 5% sample of v4 clients for the opt-out release population. We have a meeting scheduled on Aug 24 to make the decision, so that we can have everything set to go by Fx41 beta6.

Exec Summary

  • Data quality, validation
    • Team is focusing on executive dashboard roll ups in validation effort
    • added client probes to beta population to narrow down missing pings question and a few other issues
  • Added a Windows drill down for executive report data
  • Starting work on executive dashboard with combined v2 + v4 data
  • Healthreport content is up and work to use the new API is underway (no longer a big risk)
  • Proposal: if we don't feel confident turning off v2 data for Fx41, collect v4 data for 5% of the population

Risks/Issues

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/10
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/10
Data continuity across V2/V4 Open Katie/Mark/Trink Plan, Metabug 8/10
Legal review Open BDS/Legal Meeting between groups 8/10
QA sign off (functional, load) Open Stuart Telemetry/Testing 8/10
Operations - data retention requirements Open Travis/Katie Eng team owes ops a doc defining ping types and data retention requirements 8/10
Operations - analysis tools & microservices Open Travis/Mark/Roberto Architecture/Data flow diagram 8/10
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 Open 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

Accomplished for Last Period

please see http://benjamin.smedbergs.us/weekly-updates.fcgi/project/firefox-measurement

please see http://benjamin.smedbergs.us/weekly-updates.fcgi/project/firefox-measurement

Outstanding requests not yet road mapped into a release

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

Important Links/References

Retrieved from "https://wiki.allizom.org/index.php?title=Unified_Telemetry/Status_reports/August_14_2015&oldid=1090298"