Closed Bug 1310280 Opened 8 years ago Closed 8 years ago

Investigate telemetry needs for Activity Stream

Categories

(Firefox for Android Graveyard :: General, defect, P1)

All
Android
defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: sebastian, Assigned: sebastian)

References

Details

(Whiteboard: [MobileAS])

AS desktop (and soon iOS) are using the tiles pipeline for telemetry. On Android we already have a telemetry system and we need to figure out whether this is suitable for the needs of Activity Stream or whether we need to implement the same solution desktop and iOS uses. Data events: * https://github.com/mozilla/activity-stream/blob/master/data_events.md iOS client: * https://github.com/mozilla-mobile/firefox-ios/pull/2151/files * https://github.com/mozilla-mobile/onyx_ios/tree/master/OnyxClient
Assignee: nobody → s.kaspari
Status: NEW → ASSIGNED
We want to try using our existing telemetry system. For that I'll add some of the probes [1] to our prototype and then we will look at the data in re:dash and see whether we can build the reports we are interested in. [1] https://github.com/mozilla/activity-stream/blob/master/data_events.md
Iteration: --- → 1.7
Priority: P2 → P1
Iteration: 1.7 → 1.8
Iteration: 1.8 → 1.9
Iteration: 1.9 → 1.10
Iteration: 1.10 → 1.11
We have basic telemetry (some bugs are still open) and bug 1319245 is tracking the work for richer telemetry data.
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.