[https://github.com/mozilla/telemetry-streaming/issues/20 didn't get much traction, moving to bugzilla for qf triage] Bug 1344003 re-adds a dashboard for hang signature tracking targetted for engineers and performance diagnostics. For release criteria tracking and reporting we need an aggregate similar to crash aggregates that gives us hang rate per version/channel/os. Past analysis used hangs over 100ms per minute. We should review as part of this effort if there are other ways we can summarize the perceived impact of hangs that better penalizes not only the frequency but also duration of hangs. If we had data in re:dash, we don't need a separate telemetry dashboard. This would also allow aggregating
ni? :ryanvm for how this fits into the war room roadmap. This is a metric we want to track for Quantum, with diagnostic dashboards for engineers but also reporting as key metric for release and experiments.
Can this be covered as part of bug 1344003?
I can't speak to that. I'd like to let BHR be BHR and have any additional scope addressed after we have that.
Is this to be covered by Mission Control?
Mostly by BHR, Mission Control covers Input Latency. We can close this for now.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.