getsentry / getsentry/sentry-java

Add API to track screens

Aperta
#2,981 3 commenti 0 reazioni 1 assegnatario Rivendicata da @markushi Vedi su GitHub
Android Feature Spans
Lingua principale
Kotlin
Stelle
1.4k
Fork
478
Merge medio
2g 23h
PR unite (30g)
67

Descrizione

For the insights modules we want to provide metrics on a screen level. As of now, we do not track screens per se, but have automatic (idle) activity transactions which offers similar functionality.

In order to no rely too much on future performance features(like spans without transactions) we could the following:
* For every screen, create a long running transaction
* Add user interactions as spans
* Add slow/frozen frames as spans
* Add TTID/TTFD metrics to the screen txn

As a default implementation we can have an Activity based screen provider, as this would work for any Android app.

#### Implementation Details
> For every screen, create a long running transaction

It makes sense to stop the transaction as some point, so whenever the screen is closed or a timeout (30s?) is reached the txn gets finished.

> Add user interactions as spans

Right now it would create it's own idle txn, can be turned into a span instead. Should be simply enough.

> Add slow/frozen frames as spans

Should be similar to what we have right now

> Add TTID/TTFD metrics to the screen txn

This is probably the trickiest one, as the start of the TTID is the moment where the new screen isn't active yet.
If an app is activity based it works like this
1. `Activity.onPause()` is called for the old screen, --> this is the starting point of the TTID/TTFD measurement
2. New Activity is created and launched
3. New Activity.onResume is called
4. New Activity renders first frame --> end of TTID measurement

Guida per i contributori

Apri la guida per i contributori

Valutazione

Questa issue non è ancora stata valutata.

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.