1611240 - Expose gecko build id to android telemetry

Status: RESOLVED FIXED

(Core :: Graphics, enhancement)

Description

[Jeff Muizelaar [:jrmuizel]]

We want the same build id that shows up in about:support to show up in telemetry.

Comment 1

[Kris Taeleman (:ktaeleman)]

Attachment: Bug 1611240 - Adding telemetry for gecko build id and version

Comment 2

[Kris Taeleman (:ktaeleman)]

Comment on attachment 9124395 [details]
Bug 1611240 - Adding telemetry for gecko build id and version

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?

Adding gecko buildid and version will allow us to know which gecko engine version was shipped with the product using geckoview.

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:

Correlating performance/stability and usage telemetry to gecko build versions.

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

Using the application version id to try to determine gecko engine version was error prone and a manual process.

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.

Note that the data steward reviewing your request will characterize your data collection based on the highest (and most sensitive) category.

<table>
<tr>
<td>Measurement Description</td>
<td>Data Collection Category</td>
<td>Tracking Bug #</td>
</tr>
<tr>
<td>Gecko Engine Version</td>
<td>Technical data</td>
<td>1611240</td>
</tr>
<tr>
<td>Gecko Engine Buildid</td>
<td>Technical data</td>
<td>1611240</td>
</tr>
</table>

6. How long will this data be collected? Choose one of the following:

• I want to permanently monitor this data. (ktaeleman)

7. What populations will you measure?

• Which release channels?
  All

• Which countries?
  All

• Which locales?
  All

• Any other filters? Please describe in detail below.
  No

8. If this data collection is default on, what is the opt-out mechanism for users?
   Regular firefox telemetry opt-out mechanism

Comment 3

[Alessio Placitelli [:Dexter]]

Comment on attachment 9124395 [details]
Bug 1611240 - Adding telemetry for gecko build id and version

I'm not a Data Steward :-P Redirecting to chutten! See here for a list of Data Stewards ;-)

Comment 4

[Chris H-C :chutten]

PRELIMINARY NOTES:
Next time please attach the data review request as an attachment. That makes it easier for us to find it in the Data Steward worflow.

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 Telemetry so is documented in its definitions file Scalars.yaml and the Probe Dictionary. This collection is part of GV Streaming Telemetry so it is also documented in a Glean metrics.yaml.

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

Yes. This collection is Telemetry so can be controlled through Firefox's Preferences. It is also Glean, so it can be controlled via the preferences of the app embedding Glean.

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

Yes, Kris Taeleman is responsible.

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?

Default on for all channels.

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?

No. This collection is permanent.

---

Result: datareview+

Comment 5

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/4d978161c8a3
Adding telemetry for gecko build id and version r=Dexter

Comment 6

[Kris Taeleman (:ktaeleman)]

Attachment: Bug 1611240 - Fixing metrics.yaml linting errors.

Comment 7

[Cosmin Sabou [:CosminS]]

https://hg.mozilla.org/mozilla-central/rev/4d978161c8a3

Comment 8

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/7b2af1ee40d0
Fixing metrics.yaml linting errors. r=Dexter

Comment 9

[Noemi Erli[:noemi_erli]]

https://hg.mozilla.org/mozilla-central/rev/7b2af1ee40d0