6

Add error telemetry for skeleton UI

 3 years ago
source link: https://bugzilla.mozilla.org/show_bug.cgi?id=1686301
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
neoserver,ios ssh client

Comment on attachment 9197603 [details]
Bug 1686301 - Report errors in skeleton UI via telemetry r=mconley!,emalysz!

Request for data collection review form

All questions are mandatory. You must receive review from a data steward peer on your responses to these questions before shipping new data collection.

  1. What questions will you answer with this data?
    How many users are having the skeleton UI disabled for them automatically, and why?

  2. Why does Mozilla need to answer these questions? Are there benefits for users? Do we need this information to address product or business requirements? Some example responses
    Ensure that a feature which we will likely ship is actually consistently enabled for users.

  3. What alternative methods did you consider to answer these questions? Why were they not sufficient?
    Local testing. It's infeasible to replicate the variability of the wild locally.

  4. Can current instrumentation answer these questions?
    No.

  5. List all proposed measurements and indicate the category of data collection for each measurement, using the Firefox data collection categories found on the Mozilla wiki.
    Measurement Description: startup.skeleton_ui_disabled_reason - the reason why the skeleton UI was not shown to the user.
    Data Collection Category: Either 1 or 2. Some limited interaction could conceivably be inferred from some values we give, such as if the skeleton UI has been disabled by the user.
    Tracking bug #: 1686301

  6. Please provide a link to the documentation for this data collection which describes the ultimate data set in a public, complete, and accurate way.
    This collection is documented in its definitions file s Histograms.json, Scalars.yaml, and/or Events.yaml and in the Probe Dictionary at https://probes.telemetry.mozilla.org.

  7. How long will this data be collected? Choose one of the following:
    I want this data to be collected for 6 months initially (potentially renewable).

  8. What populations will you measure?

  • Which release channels?
    All.

  • Which countries?
    All.

  • Which locales?
    All.

  • Any other filters? Please describe in detail below.

  1. If this data collection is default on, what is the opt-out mechanism for users?
    Standard Firefox telemetry settings.

  2. Please provide a general description of how you will analyze this data.
    Explore the values reported via glam/tmo Measurement Dashboard/stmo.

  3. Where do you intend to share the results of your analysis?
    Likely here or in Matrix chats.

  4. Is there a third-party tool (i.e. not Telemetry) that you are proposing to use for this data collection? If so:
    No.

Additional note: There is also an additional value for this probe added in bug 1687561, queued up behind this one. It felt like a separate bug so I put it in as such, but it will report a value indicating that the skeleton UI crashed once if that ever happens for a user.


About Joyk


Aggregate valuable and interesting links.
Joyk means Joy of geeK