Send crash reports to Glean

[pocmo]

Why/User Benefit/User Problem

Crash pings would help us to calculate crash rates... something we do not get with Sentry (#2326).

Fennec implementation:
https://bugzilla.mozilla.org/show_bug.cgi?id=1407557

This is something we'd implement in the telemetry library:
https://github.com/mozilla-mobile/telemetry-android

What/Requirements

Add Glean crash reporter to CrashReporter services.

https://github.com/mozilla-mobile/android-components/tree/master/components/lib/crash#sending-crash-reports-to-glean

Acceptance Criteria (how do I know when I’m done?)

• Glean Crash reporter is added, and crash counts are being sent
• Documentation added to Fenix telemetry docs, explaining what the crash reporter collects
• Data review for adding new telemetry collection of Glean crash reporter

┆Issue is synchronized with this Jira Task

[daoshengmu]

I am curious if we already have the crash pings in Fennec that means Gecko can send the crash pings to the telemetry server (http://telemetry.mozilla.org/). So, what is the following work for android-telemetry-components? IIUC, the crash pings from Gecko could help us catch the crashes from the Gecko side, like Gecko View.

[vesta0]

No longer relevant considering sentry and crash reporting (discussed in triage)

[bbinto]

Is this still a valid issues? If so, we are aiming for crash reporting / good stats for milestone 2 or 3, so feel free to size during triage AND move it into milestone 2 backlog.

[pocmo]

Yes, this is still valid. The crash ping will help us to measure the health of the app and hopefully avoid situations like we had in Focus where we couldn't really pinpoint certain issues.

The glean, app and AC teams have met and are going to work on a solution to collect this data with Glean from the crash reporter component.

In AC that is tracked by the meta "Good crash statistics":
mozilla-mobile/android-components#1820

The related Glean issue is:
https://bugzilla.mozilla.org/show_bug.cgi?id=1522461

[vesta0]

@bbinto please advise.

[bbinto]

@pocmo can you help me understand what work is left to do for the A-C team, and Fenix, and do you have everything you need from the Glean team to send this ping?

If we don't get any update on this before sprint planning, I'm fine with moving this down the backlog for now.

/cc @vesta0

[vesta0]

Blocked by https://bugzilla.mozilla.org/show_bug.cgi?id=1522461

[liuche]

This unblocks #5113, which has a bugzilla bug.

[sblatz]

@liuche Should I put a QA needed on this?

[liuche]

Don't need a QA-label here - we'll wait for the dashboard #5113, which should be the verification. I'll close this then.