Unified Telemetry/Status reports/data continuity/November 4 2015
From MozillaWiki
Contents
Data continuity status report November 4, 2015
Overall Project Health
This week: Green
Last week: Green
Project summary
- Deliveries are the executive dashboard populated by both v2 and v4 values
- Describing explanations for why differences exist between the streams
Exec Summary
Project broken into 3 stages - POC/validation (11/12), handling unexpected differences (TBD), Operationalization (TBD).
POC:
- Executive dashboard with consolidated data set
- Plot both lines, show values on roll over (and % difference)
- High level metrics showing how much change is introduced in v4. For each measure, take last monthly value and have a table on the page. Explains the difference in the measures.
Risks/Issues
Description of Risks/Issues | State | Owner | Plan to Resolve/Mitigation | Target Date |
---|---|---|---|---|
V4 data validation | Closed | Sam | Waiting for more data; blocked on V2 outage. doc | 10/10 |
Data continuity across V2/V4 | Open | Katie/Mark/Trink | Plan, Metabug | 11/12 |
tracking ticket for dashboard | in progress | Mreid, Hamilton | bug | ASAP |
unexpected columns needs to be debugged | in progress | Mreid, Saptarshi | debug | 11/12 |
Accomplished for Last Period
- Mreid got required data
- tiger team assembled, roles understood, basic project outline and timing.
Planned for Next Period
- Mreid to get data drop
- Mark to provide example roll ups to Hamilton
- one set of data with fhr, one UT data - trink roll up of Saptarshi value
- google doc with links via Mreid
- Mark to provide Saptarshi examples of “bad lines” (too many / too few columns)