Closed Bug 1822692 Opened 1 year ago Closed 1 year ago

Add initial Telemetry for the new Migration Wizard

Categories

(Firefox :: Migration, task, P1)

task

Tracking

()

RESOLVED FIXED
113 Branch
Tracking Status
firefox113 --- fixed

People

(Reporter: mconley, Assigned: mconley)

References

(Regressed 1 open bug)

Details

Attachments

(3 files)

We'd like to know how the Migration Wizard gets invoked, and what context its in when it's used. Up until now, we've used the FX_MIGRATION_ENTRY_POINT histogram for this for the old migration wizard, but that model doesn't work when we're no longer opening a dialog window, but potentially migrating from an embedded context where the user didn't manually invoke it, like in an about:welcome onboarding card.

It also doesn't help that FX_MIGRATION_ENTRY_POINT is an old-school Histogram with 10 max values.

Having spoken to perry.mcmanis in #data-help, here's the plan:

  1. We keep the FX_MIGRATION_ENTRY_POINT mechanism for continuity and comparison between the old wizard and the new wizard, but add a new FX_MIGRATION_ENTRY_POINT_CATEGORICAL categorical histogram for the existing (and eventual) entrypoints.
  2. Continue writing to the old histogram, but also have the old wizard write into the new categorical histogram as well so we can ensure that the two histograms more or less line up.
  3. Have the new Migration Wizard only write into the new categorical histogram.

Once we're satisifed that FX_MIGRATION_ENTRY_POINT_CATEGORICAL is doing its job, we can get rid of the old FX_MIGRATION_ENTRY_POINT histogram.

Cc'ing Gijs and mak since they're both named on the original FX_MIGRATION_ENTRY_POINT histogram.

We're intentionally keeping the old FX_MIGRATION_ENTRY_POINT histogram around and
written to in order to have a smooth cutover to the new categorical histogram.

Assignee: nobody → mconley
Status: NEW → ASSIGNED
Attachment #9323362 - Flags: data-review?(jhirsch)
Severity: -- → N/A
Priority: -- → P3
Priority: P3 → P1

Comment on attachment 9323362 [details]
Data collection request.md

data-review+. Sorry for the delay here! Was out sick for part of last week.


  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, the usual desktop telemetry documentation.

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

Yes, the usual opt-out controls for telemetry.

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

Yes, mconley will monitor.

  1. 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.

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

Default-on.

  1. Does the instrumentation include the addition of any new identifiers?

No.

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

Yes.

  1. Does the data collection use a third-party collection tool?

No.

Attachment #9323362 - Flags: data-review?(jhirsch) → data-review+
Keywords: leave-open
Pushed by mconley@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/ec398cb79ad6
Introduce a categorical histogram for recording the Migration Wizard entrypoint. data-review=jhirsch, r=Gijs
Keywords: leave-open
Pushed by mconley@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/4895a0096dfe
Add tests for migration wizard entrypoint telemetry. r=Gijs
Regressions: 1823558
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → 113 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: