Unified Telemetry/Status reports/July 17 2015: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(→‎Exec Summary: update with detail)
Line 14: Line 14:
** Remaining client work ([uplift3], http://bit.ly/1TCl4r8) for 41 is manageable and either blocked by info requests or review
** Remaining client work ([uplift3], http://bit.ly/1TCl4r8) for 41 is manageable and either blocked by info requests or review
* Working toward data validation milestone on July 30: http://mzl.la/1J2OdZA
* Working toward data validation milestone on July 30: http://mzl.la/1J2OdZA
* Preparing pipeline to scale to release traffic: goal is to be ready by July 30(?)
* Pipeline scaling work to be completed by July 30(?)
* <tools>
* <tools>
* Ongoing planning on FHR V2/V3 historic pipeline migration link to status [https://mana.mozilla.org/wiki/display/PM/FHR+historic+pipeline+update+July+6 here].
* Ongoing planning on FHR V2/V3 historic pipeline migration link to status [https://mana.mozilla.org/wiki/display/PM/FHR+historic+pipeline+update+July+6 here].

Revision as of 18:10, 16 July 2015

previous weeks report

placeholder for the weeks report

Unified Telemetry status report July 17, 2015

Overall Project Health

Green -

Exec Summary

  • Not uplifting recent send logic changes to Beta (needs more bake time for confidence)
    • Uplifting a few patches around the send-logic ([uplift2], http://bit.ly/1Je45UA) to Aurora as soon as the send-logic impact is verified
    • Remaining client work ([uplift3], http://bit.ly/1TCl4r8) for 41 is manageable and either blocked by info requests or review
  • Working toward data validation milestone on July 30: http://mzl.la/1J2OdZA
  • Pipeline scaling work to be completed by July 30(?)
  • <tools>
  • Ongoing planning on FHR V2/V3 historic pipeline migration link to status here.

Risks/Issues

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

Engineering

Ops

  • 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

Retrieved from "https://wiki.mozilla.org/index.php?title=Unified_Telemetry/Status_reports/July_17_2015&oldid=1085198"