Add startup-time telemetry
Categories
(Toolkit :: Startup and Profile System, enhancement)
Tracking
()
People
(Reporter: jhirsch, Unassigned)
References
Details
Followup from bug 1927605.
At early startup, before a profile has been selected, the profile selector window is shown and the user can (1) check or uncheck the 'show at startup' checkbox, and (2) choose a profile.
Once the user chooses a profile, Firefox exits and restarts into that profile.
Glean can record probes in early startup then replay them in later startup--but because we don't startup into a profile, but instead restart into a profile, that early startup Glean data will be dropped.\
There is currently very limited legacy telemetry data recorded in this pre-startup setting by the legacy profiles code, it is recorded by setting an environment variable that is read back in on restart. We may want to extend the existing set of early startup-time profiles telemetry to include showing the profile selector window as one of the recorded options, so that we can count how often this window is shown at startup. We may also want to migrate this data from legacy telemetry to Glean.
While we could extend this early startup-time strategy to record additional probes, I'm not sure how much value we'd get from doing so.
If the user selects a profile, then we restart into that profile, so we will already know which profile was launched because it will run.
Once we fix bug 1942384, the user could launch a profile into the edit or delete screens. These screens are instrumented, so we will already be able to observe if these screens are loaded close to startup (small value of the client_time, which records time elapsed since startup).
The one bit of data we would otherwise lose is whether the user toggled the 'show on startup' checkbox in the startup-time dialog.
We'll need input from product and possibly data science to decide the priority here.
Description
•