Skip to content
This repository has been archived by the owner on Nov 1, 2022. It is now read-only.

Telemetry probe to measure alive tabs #9997

Closed
fluffyemily opened this issue Mar 30, 2021 · 5 comments
Closed

Telemetry probe to measure alive tabs #9997

fluffyemily opened this issue Mar 30, 2021 · 5 comments
Assignees

Comments

@fluffyemily
Copy link

fluffyemily commented Mar 30, 2021

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:

  • number of alive tabs when
    • going to background
    • going back to foreground and how long we've been backgrounded (so we can plot tab retention with 1,5,10,30 minutes)

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

@pocmo pocmo self-assigned this Mar 30, 2021
@pocmo
Copy link
Contributor

pocmo commented Mar 31, 2021

I wrote a patch that gathers the following data when the app goes to foreground/background:

----------------------
Background:
      Active tabs:  8
      Crashed tabs: 0
      Total tabs:   8
----------------------
Foreground:
      Active tabs:  4
      Crashed tabs: 0
      Total tabs:   8
----------------------
Time in background: 80288 ms
Active tab diff:    -4
Crashed tab diff:   0
Total tab diff:     0

@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?

@dblohm7
Copy link

dblohm7 commented Mar 31, 2021

@pocmo LGTM!

As for the analysis bit, I would suggest asking on #glam in slack, they've been helpful to me in the past.

@pocmo
Copy link
Contributor

pocmo commented Apr 1, 2021

After asking in #data-help, using an event with extras seems to be the right choice.

@pocmo
Copy link
Contributor

pocmo commented Apr 9, 2021

Probe landed in Fenix and should be in the next Nightly build.

@pocmo pocmo closed this as completed Apr 9, 2021
@dblohm7
Copy link

dblohm7 commented Apr 12, 2021

\o/ Thanks @pocmo !

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants