Unified Telemetry/Status reports/July 10 2015

From MozillaWiki
Jump to: navigation, search

previous weeks report

Unified Telemetry status report July 10, 2015

Overall Project Health

Red - Development work is near completion (expected next week). The validation work required to be confident enough to turn off the FHR mechanism will exceed the amount of time remaining in the cycle. Unified telemetry's target for turning off FHR and collecting opt-out telemetry information from the release population is now r41. The pipeline has been in production and collecting pre-release UT data; it's ready for other types of production traffic (e.g. FxOS pings and cloud service log data).

Exec Summary

  • Ongoing effort to validate data from nightly, aurora and beta channels
  • Ongoing effort to prepare pipeline to scale to release traffic
  • Ongoing effort to make telemetry tools and APIs work with v4 data
  • Working on a mitigation plan for projects that were hoping to analyze release population data in r40
    • Data available from nightly, aurora and beta channels now; analysis can begin
    • Create python notebooks with example code for these projects
  • Re-prioritizing two visualization projects that make use of pre-release data:
  • Ongoing planning on FHR V2/V3 historic pipeline migration link to status here.
  • Creation of milestones and plan for r41 delivery begins


Description of Risks/Issues State Owner Plan to Resolve/Mitigation Target Date
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 7/15
Data continuity across V2/V4 Open Katie/Mark/Trink Mark writing up plan from Whistler; metrics team specifying data sets and reviewing "executive" data set. https://bugzilla.mozilla.org/show_bug.cgi?id=1182684 7/15
Legal review Open BDS/Legal Meeting between groups 8/04
QA sign off (functional, load) Open Stuart Working with QA on creating test cases/test plans 8/04
Operations - data retention requirements Open Travis/Katie Eng team owes ops a doc defining ping types and data retention requirements 8/04
Operations - analysis tools & microservices Open Travis/Mark/Roberto Architecture/Data flow diagram; meeting next Monday (7/13) 8/04
Data loss incident Open 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/Georg Made a request to Laura Thomson for help 8/04
Budget, size of UT pings Open Mark/BDS https://bugzilla.mozilla.org/show_bug.cgi?id=1182693 8/04
Analysis difficulty Open Katie/tbd No plan yet, aside from ongoing work on tools 8/04

Accomplished for Last Period

Planned for Upcoming Period



  • Meeting to go over Telemetry tools/microservices production deployment
  • Continued work on scaling for release loads

Project Management

  • create meeting for legal review
  • follow up with ops and qa
  • mitigation plan for projects depending on UT
  • reassess milestones given schedule adjustment

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