Telemetry to Crash Reporting Page

[sblatz]

Measure tracking to and within the crash reporting page

What questions will you answer with this data?

• Define stability
• How often the crash page shows up per user/per day etc
• Understand if/how often users feel like sharing this data with us

Why does Mozilla need to answer these questions? Are there benefits for users? Do we need this information to address product or business requirements?

• One of the measurements of tracking the stability of the app is to collect telemetry on the crash reporting page

What probes (suggested, if applicable)

• when this page/crash page is being loaded/shown
• track toggle on "send crash report to Mozilla"

Dependencies (Added by PM and Eng)

• Glean SDK

Acceptance Criteria (Added by PM)

• Event pings can be queried via re:dash
• We are sending telemetry events for the actions listed in the requirements
• We have documented the telemetry
• We have asked a data steward to review the telemetry
• NOT an AC: Data science to create dashboard or further graphs (this will be a separate issue, this issue is only about hooking up the events described and that they can be queried in re-dash)

┆Issue is synchronized with this Jira Task

[sblatz]

@boek how should I go about using boolean values with this change? 4cad242

[sblatz]

DRAFT

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?

• Define stability
• How often the crash page shows up per user/per day etc
• Understand if/how often users feel like sharing this data with us

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?

• One of the measurements of tracking the stability of the app is to collect telemetry on the crash reporting page

3. What alternative methods did you consider to answer these questions? Why were they not sufficient?

• N/A (These are baseline metrics)

4. Can current instrumentation answer these questions?

• Currently no, as these are some of the first metrics we're recording

5. List all proposed measurements and indicate the category of data collection for each measurement, using the Firefox data collection categories on the found on the Mozilla wiki.

• All data is Category 2.

6. How long will this data be collected?

• @mmccorks will permanently monitor this data.

7. What populations will you measure?

• All release, beta, and nightly users with telemetry enabled.

8. Please provide a general description of how you will analyze this data.

• Leanplum
• Glean

9. Where do you intend to share the results of your analysis?

• Only on leanplum, glean and with mobile teams.