1553935 - Add a Glean crash count metric to android-components/lib-crash

Status: RESOLVED FIXED

(Data Platform and Tools :: Glean: SDK, task, P1)

Description

[Travis Long [:travis_]]

This instruments the uncaught exception and native code crash types that are handled in android-components/lib-crash. This includes adding a Glean CrashReporterService to handle recording to the counter metrics.

See also bug 1522461 for more crash related info.

Comment 1

[Travis Long [:travis_]]

Attachment: GitHub Pull Request

This is still a DRAFT PR!

Comment 2

[Travis Long [:travis_]]

Adding data review request as attachment below:

Comment 3

[Travis Long [:travis_]]

Attachment: GleanCrashCounts.md

Comment 4

[Chris Peterson [:cpeterson]]

Adding the [geckoview:fenix:m8] whiteboard tag because we would like to start monitoring Fenix and GeckoView crash rates in Q3.

Comment 5

[Travis Long [:travis_]]

Adding this question to the d?, as posed by :Dexter

Comment 6

[Chris H-C :chutten]

Comment on attachment 9073550 [details]
GleanCrashCounts.md

DATA COLLECTION REVIEW RESPONSE:

    Is there or will there be documentation that describes the schema for the ultimate data set available publicly, complete and accurate?

Yes. This collection is Glean so is documented in its definitions file [metrics.yaml](https://github.com/mozilla-mobile/android-components/tree/master/components/lib/crash).

    Is there a control mechanism that allows the user to turn the data collection on and off?

Yes. Embedding applications are required to provide user control for data collection.

    If the request is for permanent data collection, is there someone who will monitor the data over time?

This will be handled by the embedding application.

    Using the category system of data types on the Mozilla wiki, what collection type of data do the requested measurements fall under?

Category 1, Technical.

    Is the data collection request for default-on or default-off?

Depends on the embedding application.

    Does the instrumentation include the addition of any new identifiers?

No.

    Is the data collection covered by the existing Firefox privacy notice?

Yes.

    Does there need to be a check-in in the future to determine whether to renew the data?

N/A. This Data Review is for the data collection mechanism, not the collection itself.

---
Result: datareview+

Comment 7

[Travis Long [:travis_]]

Closing this as the implementation is complete. I've opened Bug 1566169 to track implementing this in the Reference Browser.