-
Notifications
You must be signed in to change notification settings - Fork 473
Telemetry probe to measure alive tabs #9997
Comments
I wrote a patch that gathers the following data when the app goes to foreground/background:
@dblohm7 Does this data cover what you need here? I am not really sure yet how to map this to metrics in Glean. My guess is that we could record this as a single event (when the app comes to the foreground) and attach the data as extras. But I am not sure if this will be the best way for analyzing this data. @fluffyemily Do we have someone who can help us with getting this data analyzed / plotted and who may have an idea how to best model it for that? I assume that GLAM won't be sufficient and we may need some custom dashboard on Redash? |
@pocmo LGTM! As for the analysis bit, I would suggest asking on #glam in slack, they've been helpful to me in the past. |
After asking in |
Probe landed in Fenix and should be in the next Nightly build. |
\o/ Thanks @pocmo ! |
Individual issue to track new telemetry related to page persistence metrics.
We would like a new telemetry probe to measure alive tabs when the app is moved from to the foreground from the background. We would like to measure:
This metrics could help us track how memory/performance affects retaining tabs/getting killed and how often our users get their tabs reloaded. Also it can help us know how many tabs are actually alive in users devices (e.g. when thinking about memory/performance tradeoffs based on number of tabs)
┆Issue is synchronized with this Jira Task
The text was updated successfully, but these errors were encountered: