Unified Telemetry/Status reports/July 10 2015
Jump to navigation
Jump to search
Unified Telemetry status report July 10, 2015
Overall Project Health
Red - Development work reaches completion. Validation work required will exceed amount of time remaining in the cycle. r41 becomes Unified telemetries go live target.
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:
- https://bugzilla.mozilla.org/show_bug.cgi?id=1160626 (Map prerelease to release populations)
- https://bugzilla.mozilla.org/show_bug.cgi?id=1160636 (Allow query of "how many users of type X")
- Ongoing planning on FHR V2/V3 historic pipeline migration link to status here.
- creation of milestones and plan for r41 delivery begins
Risks/Issues
| Description of Risks/Issues | State | Owner | Plan to Resolve/Mitigation | Target Date |
|---|---|---|---|---|
| Data integrity between V2/V4 | Open | Brendan/Sam | Investigation in progress. Added resources (Sam). | Example |
| Data continuity across V2/V4 | Open | Katie/TBD | Metrics team reviewing executive dashboard work; Metrics team specifying additional rollup tables; Conversations next week to start implementing plans discussed at Whistler. | Example |
| Internal data consistency (v4) | Open | Sam/Brendon | Investigations underway | Example |
| Legal review | Open | BDS/Legal | Meeting between groups | Example |
| QA sign off (functional, load) | Open | Stuart | Working with QA on creating test cases/test plans | Example |
| Operations - data retention requirements | Open | Travis/Katie | Eng team owes ops a doc defining ping types and data retention requirements | Example |
| Operations - analysis tools & microservices | Open | Travis/Katie | Eng team to provide architecture and data flow, Ops figures out micro services needed | Example |
| Data loss issue last week | Open | mreid/whd/trink | Tee server needs to return error status from old or new. Added Ops resources (Daniel Thornton). | Example |
| Remote about:healthreport content | Open | Katie/Georg | Made a request to Laura Thomson for help | Example |
| Example | Example | Example | Example | Example |
Accomplished for Last Period
- Data validation from beta stream
- Tagged/sorted validation tickets
Planned for Upcoming Period
Engineering
- Python notebooks
- Data validation
- compare v2/v4 rollups for dashboards
Ops
- Tooling
- microservices
Performance
- items
QA
- test cases and testing
Project Management
- create meeting for legal review
- follow up with ops and qa
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 |