Closed Bug 1156358 Opened 9 years ago Closed 5 years ago

Telemetry redesign: Centralize scheduler, init & ping triggering logic in TelemetryController.jsm

Categories

(Toolkit :: Telemetry, defect, P4)

Product:
Toolkit
Component:
Telemetry
Type:
defect
Points:
2

Tracking

()

Status:
RESOLVED FIXED
Tracking Flags:
Tracking Status
firefox40 --- affected

People

(Reporter: gfritzsche, Unassigned)

References

Details

(Whiteboard: [unifiedTelemetry] [measurement:client]) 

Per: https://docs.google.com/document/d/1lKRfNl5aJ0W2flOp67Y5O3WDz2dSSz7a6r23DQ89poU/edit?pli=1

Note that:
* TelemetryStorage is already being separated per bug 1156355 & bug 1150134
* Factoring out TelemetrySend (send queue and ping send logic) is for another bug
* submitExternalPing() is already done by bug 1150134
Blocks: 1156359
Blocks: 1156360
No longer blocks: 1156359
Whiteboard: [b5] [unifiedTelemetry]
This should also make TelemetryController trigger TelemetrySession.setup() (instead of TelemetrySession being initialized independently by profile-after-change).
Whiteboard: [b5] [unifiedTelemetry] → [unifiedTelemetry]
(In reply to Georg Fritzsche [:gfritzsche] from comment #1)
> This should also make TelemetryController trigger TelemetrySession.setup()
> (instead of TelemetrySession being initialized independently by
> profile-after-change).

That part is bug 1145188.
Points: --- → 2
Priority: -- → P2
Whiteboard: [unifiedTelemetry] → [unifiedTelemetry] [measurement:client]
Priority: P2 → P3
Priority: P3 → P4
This work can be considered no longer relevant (and mostly complete)
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.