Unified Telemetry/Status reports/EventTelemetry/Sept 7 2016: Difference between revisions
(→Exec Summary: high level) |
|||
| (4 intermediate revisions by the same user not shown) | |||
| Line 9: | Line 9: | ||
=== Exec Summary === | === Exec Summary === | ||
* Project | * Project remains in yellow as we continue to understand dependencies and address architectural issues | ||
* | ** DB vs black box being sketched out via shim | ||
* | * FF client side work begins next week | ||
* | * Meetings with AS folks | ||
=== Risks/Issues === | === Risks/Issues === | ||
| Line 24: | Line 24: | ||
|- | |- | ||
| Assess what event measurements in Activity Stream can be measured via the Event Telemetry approach | | 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 | | Escalate request for UX feedback to Product and Data leadership | ||
|| In process || Katie || Escalation || | || In process || Katie || Escalation || In flight | ||
|- | |- | ||
| event registry integration in add-ons | | event registry integration in add-ons | ||
|| | || Done || Georg || seek consensus || Done | ||
|- | |- | ||
|} | |} | ||
=== Accomplished for Last Period === | === Accomplished for Last Period === | ||
* | * Assessed what event measurements in Activity Stream can be measured via the Event Telemetry approach | ||
* | * process defined for the event registry integration in add-ons (glind, mattg, mark banner) | ||
* | ** reached out, on-board so far: addons team, mbanner, test-pilot | ||
* ongoing discussion around architectural issues DB vs. blackbox | |||
* Ilana recommends reimplement everything that is in AS in event based telemetry | |||
* Event Telemetery - First prototype is AS (no requirement to use data platform pipeline) | |||
=== Planned for Next Period === | === Planned for Next Period === | ||
* | * Ilana set up a meeting with Marina/Georg/Ilana | ||
* | *DB vs. blackbox | ||
* | ** Georg to sketch it out prototype/shim implementation in test pilot and work with will | ||
* Thomas and Katie to work on event / probe dependencies matrix | |||
* Firefox client-side work starting next week | |||
** Georg & Ilana to meet to clear up last detail questions on event draft | |||
** Risk - Still missing a "prototype" project to guide the work from | |||
* KP to email Tim Spurway wrt to AS | |||
=== Proposed development stages and status === | === Proposed development stages and status === | ||
Latest revision as of 17:14, 8 September 2016
[previous weeks report]
Event Telemetry status report Sept 7, 2016
Overall Project Health
Last week: Yellow
This week: Yellow
Exec Summary
- Project remains in yellow as we continue to understand dependencies and address architectural issues
- DB vs black box being sketched out via shim
- FF client side work begins next week
- Meetings with AS folks
Risks/Issues
| Description of Risks/Issues | State | Owner | Plan to Resolve/Mitigation | Target Date |
|---|---|---|---|---|
| Get sign off on proposal | In process | Georg | sign offs required from TestPilot (Will Clouser), Ilana, RobFromBRC, John Dorlus, | ASAP |
| Notify Org post signoff | TBD | Thomas/Georg | Notify FX-Team, UITour stakholders, Jared, Mike Connoly | TBD |
| 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
- Assessed what event measurements in Activity Stream can be measured via the Event Telemetry approach
- process defined for the event registry integration in add-ons (glind, mattg, mark banner)
- reached out, on-board so far: addons team, mbanner, test-pilot
- ongoing discussion around architectural issues DB vs. blackbox
- Ilana recommends reimplement everything that is in AS in event based telemetry
- Event Telemetery - First prototype is AS (no requirement to use data platform pipeline)
Planned for Next Period
- Ilana set up a meeting with Marina/Georg/Ilana
- DB vs. blackbox
- Georg to sketch it out prototype/shim implementation in test pilot and work with will
- Thomas and Katie to work on event / probe dependencies matrix
- Firefox client-side work starting next week
- Georg & Ilana to meet to clear up last detail questions on event draft
- Risk - Still missing a "prototype" project to guide the work from
- KP to email Tim Spurway wrt to AS
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 |