845558 - Add telemetry to verify the idle service is behaving properly in the wild

Status: NEW

(Core :: Widget, defect)

Description

[Marco Bonardo [:mak]]

Writing tests for idle is hard, and writing a harness with dedicated tinderboxes may be quite resource expensive.
A simple alternative could be to add some telemetry to the idle service that can be tracked and would allow us to figure out if it's working as expected.

Comment 1

[:Irving Reid (No longer working on Firefox)]

Is this a dup of the reporting part of bug 844325 or do we want to move the work over to this bug?

Comment 2

[:Gavin Sharp [email: [e-mail]]]

Bug 844325 seems specific to identifying failures in Telemetry reporting in general (the idle service being one possible source of failure), whereas this bug's goal is to implement telemetry probes to track failures of the idle service specifically. Given Telemetry's use of the idle service I guess there is a bit of inter-dependency there, though, which makes things confusing!