Unified Telemetry/Status reports/EventTelemetry/Oct 12 2016
From MozillaWiki
[previous weeks report]
Contents
Event Telemetry status report October 12, 2016
Overall Project Health
Last week: Yellow
This week: Green
Exec Summary
- Project in Green (no known blockers)
- Ongoing work with test pilot (multiple methods per event)
- investigation of other companies analytics event tracking completed (no action required)
- Synch stakeholders added to meeting as next consumer. Deliverables and timing TBD
Risks/Issues
| Description of Risks/Issues | State | Owner | Plan to Resolve/Mitigation | Target Date |
|---|---|---|---|---|
| Get sign off on proposal | done | Georg | sign offs required from TestPilot (Will Clouser), Ilana, RobFromBRC, John Dorlus, | done |
| Notify Org post signoff | done | Thomas/Georg | Notify FX-Team, UITour stakholders, Jared, Mike Connoly | done |
| Assess what event measurements in Activity Stream can be measured via the Event Telemetry approach | done | Ilana | Investigate | done |
| Escalate request for UX feedback to Product and Data leadership | In process | Katie | Escalation | In flight |
| event registry integration in add-ons | Done | Georg | seek consensus | Done |
Accomplished for Last Period
- blackbox sketch, multiple methods per event needs sketching out, meet with wil if still unclear
updated, waiting for wils feedback katie/thomas: talk with AS to clear up timeline and resource expectations marina/ilana: review AS matchup georg/sunah: match up example data formats with our event format Proposed format change: reflecting two-level hierarchies in "method" or "object" field is awkward instead want to submit "category" separately old: [ts, method, object, value, extra] new: [ts, category, method, object, value, extra]
Planned for Next Period
- Wils feedback on blackbox sketch
- Client work (impacted by work in Munich this week)
- start understanding impact of sych being next consumer (Sync Team: Send Tab Analysis Plan)
Proposed development stages and status
| Stage | State | description | Target Date |
|---|---|---|---|
| Proposal creation | Done | accepted | August 1, 2016 |
| Kick off | Done | RACI + develpoment stages | August 14, 2016 |
| Development to allow test pilot to begin using and submitting | TBD | ingestion, storage, make available for analysis | TBD |
| QA Validation | TBD | Test to validate UITelemtry | TBD |
| Processing | TBD | TBD | TBD |
| Tooling | TBD | TBD | TBD |
Probe / Event dependancies and timeline
| Name of probe | design and review | Use cases / questions | list of events & priorities for implementation | who implements and owns the probe | who owns analysis |
|---|---|---|---|---|---|
| Activity Stream Events | design | use cases | event list | implement and own | analysis owner |
| UItelemetry Events | design | use cases | event list | implement and own | analysis owner |
| Search events | design | use cases | event list | implement and own | analysis owner |
| Engagement measures events | design | use cases | event list | implement and own | analysis owner |
| Test pilot events | design | use cases | event list | implement and own | analysis owner |
| Mobile Telemetry | design | use cases | event list | implement and own | analysis owner |
