Prolong the life of some migration telemetry histograms and update their metadata
Categories
(Firefox :: Migration, defect, P2)
Tracking
()
People
(Reporter: MattN, Assigned: MattN)
References
()
Details
(Whiteboard: [passwords:management] [skyline])
Attachments
(2 files)
5.45 KB,
text/plain
|
chutten
:
data-review+
|
Details |
47 bytes,
text/x-phabricator-request
|
lizzard
:
approval-mozilla-beta+
|
Details | Review |
We just changed the UI to access migration from the login management UI (since we switched to about:logins it is more buried) and we also now expose that UI for macOS with the implementation of import from Chrome in bug 1423714. It would be useful to be able to monitor both of these changes for some period of time after launch to ensure things are working as expected but the current probes have expired.
Assignee | ||
Comment 1•5 years ago
|
||
Comment 2•5 years ago
|
||
Comment on attachment 9095913 [details] Request for data collection review form 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 [Histograms.json](https://hg.mozilla.org/mozilla-central/file/tip/toolkit/components/telemetry/Histograms.json) and the [Probe Dictionary](https://telemetry.mozilla.org/probe-dictionary/). 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. If the request is for permanent data collection, is there someone who will monitor the data over time? No. This collection will expire in six months. 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. 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? Yes. MattN is responsible for renewing or removing the collection before it expires in six months. --- Result: datareview+
Assignee | ||
Comment 3•5 years ago
|
||
Pushed by mozilla@noorenberghe.ca: https://hg.mozilla.org/integration/autoland/rev/6f53a6608bcb Prolong the life of some migration telemetry histograms and update their metadata. r=Gijs
Assignee | ||
Comment 5•5 years ago
|
||
Comment on attachment 9096566 [details]
Bug 1584261 - Prolong the life of some migration telemetry histograms and update their metadata. r=Gijs
Beta/Release Uplift Approval Request
- User impact if declined: Won't be able to monitor success of bug 1423714 along with other migrators.
- Is this code covered by automated tests?: Yes
- Has the fix been verified in Nightly?: No
- Needs manual test from QE?: No
- If yes, steps to reproduce:
- List of other uplifts needed: None
- Risk to taking this patch: Low
- Why is the change risky/not risky? (and alternatives if risky): These are existing probes, all I'm doing is extending the expiration (and updating other metadata to be more specific after an automated rewrite added new fields). There are no code changes. These probes have already been tested and the data has already been analyzed years ago.
- String changes made/needed: None
Comment 6•5 years ago
|
||
bugherder |
Comment 7•5 years ago
|
||
Comment on attachment 9096566 [details]
Bug 1584261 - Prolong the life of some migration telemetry histograms and update their metadata. r=Gijs
Extending the dates & adding Matt to alerts. LGTM. Let's take this for beta 11.
Comment 8•5 years ago
|
||
bugherder uplift |
Description
•