Closed Bug 1324525 Opened 7 years ago Closed 7 years ago

Migration telemetry set to expire in 53

Categories

(Firefox :: Migration, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
Firefox 53
Tracking Status
firefox53 --- fixed

People

(Reporter: Gijs, Assigned: Gijs)

Details

Attachments

(1 file)

The following histograms will be expiring on 2017-01-23, and should be removed from the codebase, or have their expiry versions updated:

* FX_MIGRATION_ENTRY_POINT expires in version 53.0a1 - Where the migration wizard was entered from. 0=Other/catch-all, 1=first-run, 2=refresh-firefox, 3=Places window, 4=Password manager
* FX_MIGRATION_ERRORS expires in version 53.0a1 - Errors encountered during migration in buckets defined by the datatype, keyed by the string description of the browser.
* FX_MIGRATION_IMPORTED_HOMEPAGE expires in version 53.0a1 - Whether the homepage was imported during browser migration. Only available on release builds during firstrun.
* FX_MIGRATION_SOURCE_BROWSER expires in version 53.0a1 - The browser that data is pulled from. The values correspond to the internal browser ID (see MigrationUtils.jsm)
* FX_MIGRATION_USAGE expires in version 53.0a1 - Usage of migration for each datatype when migration is run through the post-firstrun flow which allows individual datatypes, keyed by the string description of the browser.
* FX_STARTUP_MIGRATION_AUTOMATED_IMPORT_PROCESS_SUCCESS expires in version 53.0a1 - Where automatic migration was attempted, indicates to what degree we succeeded. Values 0-25 indicate progress through the automatic migration sequence, with 25 indicating the migration finished. 26 is only used when the migration produced errors before it finished.
* FX_STARTUP_MIGRATION_AUTOMATED_IMPORT_UNDO expires in version 53.0a1 - Where undo of the automatic migration was attempted, indicates to what degree we succeeded to undo. 0 means we started to undo, 5 means we bailed out from the undo because it was not possible to complete it (there was nothing to undo or the user was signed in to sync). All higher values indicate progression through the undo sequence, with 30 indicating we finished the undo without exceptions in the middle.
* FX_STARTUP_MIGRATION_BROWSER_COUNT expires in version 53.0a1 - Number of browsers from which the user could migrate on initial profile migration. Only available on release builds during firstrun.
* FX_STARTUP_MIGRATION_DATA_RECENCY expires in version 53.0a1 - The 'last modified' time of the data we imported on the initial profile migration (time delta with 'now' at the time of migration, in hours). Collected for all browsers for which migration data is available, and stored keyed by browser identifier (e.g. 'ie', 'edge', 'safari', etc.).
* FX_STARTUP_MIGRATION_EXISTING_DEFAULT_BROWSER expires in version 53.0a1 - The browser that was the default on the initial profile migration. The values correspond to the internal browser ID (see MigrationUtils.jsm)
* FX_STARTUP_MIGRATION_USED_RECENT_BROWSER expires in version 53.0a1 - Whether the browser we migrated from was the browser with the most recent data. Keyed by that browser's identifier (e.g. 'ie', 'edge', 'safari', etc.).
We probably don't need all of these, but probably do still need some of them. Ni me to figure out which are still needed and prolong those probes' lifetime.
Flags: needinfo?(gijskruitbosch+bugs)
Assignee: nobody → gijskruitbosch+bugs
Status: NEW → ASSIGNED
Flags: needinfo?(gijskruitbosch+bugs)
Comment on attachment 8824109 [details]
Bug 1324525 - increment (and unify) telemetry max version for migration-related telemetry probes,

https://reviewboard.mozilla.org/r/102664/#review103414
Attachment #8824109 - Flags: review?(benjamin) → review+
Pushed by gijskruitbosch@gmail.com:
https://hg.mozilla.org/integration/autoland/rev/97157c25c4a0
increment (and unify) telemetry max version for migration-related telemetry probes, r=bsmedberg
https://hg.mozilla.org/mozilla-central/rev/97157c25c4a0
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 53
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: