1843126 - Add telemetry when pref change causes experiment unenrollment

Status: RESOLVED FIXED

(Firefox :: Nimbus Desktop Client, enhancement, P1)

Description

[dberry]

Currently, when a changed pref causes an unenrollment we record an unenrollment event with the changedPref reason. However, some experiments can change multiple prefs so it's not possible to know which pref was changed (causing the unenrollment). It would be helpful to add extra information to the unenrollment event detailing which changed pref caused the unenrollment

Comment 1

[Beth Rennie [:beth] (she/her)]

Attachment: data-review-1843126.md

Comment 2

[Beth Rennie [:beth] (she/her)]

Attachment: Bug 1843126 - Report prefs that cause experiment unenrollment r?emcminn

Comment 3

[Elise Richards]

Comment on attachment 9343774 [details]
data-review-1843126.md

Data Review Form

1. Is there or will there be documentation that describes the schema for the ultimate data set in a public, complete, and accurate way?

   • Yes, through the definition files Histograms.json, Scalars.yaml, and/or Events.yaml, and in the Probe Dictionary

2. Is there a control mechanism that allows the user to turn the data collection on and off? (Note, for data collection not needed for security purposes, Mozilla provides such a control mechanism) Provide details as to the control mechanism available.

   • Yes, through the normal telemetry opt-out.

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

   • Yes, this a permanent annotation. Barret Rennie ([e-mail]) will monitor.

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

   • Category 2 - interaction data

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

   • Default-on.

6. Does the instrumentation include the addition of any new identifiers (whether anonymous or otherwise; e.g., username, random IDs, etc. See the appendix for more details)?

   • No

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

   • Yes

8. Does the data collection use a third-party collection tool? If yes, escalate to legal.

   • No

Result

data-review+

Comment 4

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/c7a65caa82de
Report prefs that cause experiment unenrollment r=emcminn

Comment 5

[Natalia Csoregi [:nataliaCs]]

https://hg.mozilla.org/mozilla-central/rev/c7a65caa82de