(In reply to Mike Conley (:mconley) (:⚙️) from comment #6) > Via bug 1690096 comment 5, it sounds like we still want the measurement, so unless Jens' position has changed, Option 1 is likely out. Well, that has been 3 years ago. I am not aware of anybody really looking at that telemetry these days, and as it is also pretty unreliable (see bug 1768795) and hard to interpret probably no one should, at least in its current state. We mostly act on shutdown problems only when we see a crash due to a hang for a given phase, AFAICS. > The lateness guarantee on Glean in Firefox Desktop is now `XPCOMShutdown` IIUC, we currently do not collect any data [later than `XPCOMShutdown`](https://searchfox.org/mozilla-central/rev/6b8a3f804789fb865f42af54e9d2fef9dd3ec74d/toolkit/components/terminator/TerminatorTelemetry.sys.mjs#44-48) anyways, so that would not be a limiting constraint if we want to keep it, I think. But if it is easier to remove it entirely, I am not opposed.
Bug 1879136 Comment 7 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Mike Conley (:mconley) (:⚙️) from comment #6) > Via bug 1690096 comment 5, it sounds like we still want the measurement, so unless Jens' position has changed, Option 1 is likely out. Well, that has been 3 years ago. I am not aware of anybody really looking at that telemetry these days, and as it is also pretty unreliable (see bug 1768795) and hard to interpret probably no one should, at least in its current state. We mostly act on shutdown problems only when we see a crash due to a hang for a given phase, AFAICS. > The lateness guarantee on Glean in Firefox Desktop is now `XPCOMShutdown` IIUC, we currently do not collect any data [later than `XPCOMShutdown`](https://searchfox.org/mozilla-central/rev/6b8a3f804789fb865f42af54e9d2fef9dd3ec74d/toolkit/components/terminator/TerminatorTelemetry.sys.mjs#44-48) anyways, so that would not be a limiting constraint if we want to keep it, I think. But if it is easier to remove it entirely, I am not opposed. As bug 1768795 there might be some other old, related bugs we can close this way, too.