For #20127: remove app_opened_all_startup from metrics.yaml.

upstream-sync
Michael Comella 3 years ago committed by mergify[bot]
parent be64ee4159
commit 7f4ac14f66

@ -8,81 +8,6 @@ no_lint:
- CATEGORY_GENERIC
events:
app_opened_all_startup:
type: event
description: |
**This probe has a known flaw:** for COLD start up, it doesn't take into
account if the process is already running when the app starts, possibly
inflating results (e.g. a Service started the process 20min ago and only
now is HomeActivity launching). See the `cold_*_app_to_first_frame` probes
for a replacement.
<br><br>
A user opened the app to the HomeActivity. The HomeActivity
encompasses the home screen, browser screen, settings screen,
collections and other screens in the nav_graph.
This differs from the app_opened probe because it measures all
startups, not just cold startup. Note: There is a short gap
between the time application goes into background and the time
android reports the application going into the background.
Note: This metric does not record souce when app opened from
task switcher: open application -> press home button -> open
recent tasks -> choose fenix. In this case will report
[source = unknown, type = hot, has_saved_instance_state = false].
extra_keys:
type:
description: |
the startup type for opening fenix. the application and HomeActivity
either needs to be created or started again. possible values are
`cold`, `warm`, `hot` or `error`. Error is for impossible cases.
Please file a bug if you see the error case.
app created AND HomeActivity created = cold
app started AND HomeActivity created = warm
app started AND HomeActivity started = hot
app created AND HomeActivity started = error
Some applications such as gmail launches the default browser in the
background. So when we eventually click a link, browser is already
started in the background. This means that custom_tab will mostly
report `warm` startup type.
source:
description: |
The method used to open Fenix. Possible values are `app_icon`,
`custom_tab`, `link` or `unknown`. unknown is for startup sources
where we can't pinpoint the cause. One UNKNOWN case is the app
switcher where we don't know what variables to check to ensure this
startup wasn't caused by something else.
has_saved_instance_state:
description: |
boolean value whether or not startup type has a savedInstance.
using savedInstance, HomeActivity's previous state can be restored.
This is an optional key since it is not applicable to all the cases.
for example, when we are doing a hot start up, we cant have a
savedInstanceState therefore we report only [APP_ICON, HOT] instead
of [APP_ICON, HOT, false].
first_frame_pre_draw_nanos:
description: |
the number of nanoseconds the application took to launch. This is the
time difference between application launch(user pressing app_icon,
launching a link) and until the first view is about to be drawn
on the screen. If the time is not captured, this extra key will
not be reported.
bugs:
- https://github.com/mozilla-mobile/fenix/issues/11830
- https://github.com/mozilla-mobile/fenix/issues/12573
- https://github.com/mozilla-mobile/fenix/pull/13494
- https://github.com/mozilla-mobile/fenix/issues/10069
- https://github.com/mozilla-mobile/fenix/issues/19923
data_reviews:
- https://github.com/mozilla-mobile/fenix/pull/12114#pullrequestreview-445245341
- https://github.com/mozilla-mobile/fenix/pull/13958#issuecomment-676857877
- https://github.com/mozilla-mobile/fenix/pull/13494#pullrequestreview-474050499
- https://github.com/mozilla-mobile/fenix/pull/15605#issuecomment-702365594
- https://github.com/mozilla-mobile/fenix/pull/19924#issuecomment-861423789
data_sensitivity:
- interaction
notification_emails:
- esmyth@mozilla.com
- perf-android-fe@mozilla.com
expires: "2021-12-01"
app_received_intent:
type: event
description: |

Loading…
Cancel
Save