Remove or update probes expiring in Firefox 88: WEBAUTHN_*
Categories
(Core :: DOM: Web Authentication, task, P1)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr78 | --- | unaffected |
| firefox85 | --- | unaffected |
| firefox86 | --- | unaffected |
| firefox87 | + | fixed |
People
(Reporter: telemetry-probes, Assigned: rmf)
References
Details
(Whiteboard: [probe-expiry-alert])
Attachments
(2 files)
|
291 bytes,
text/plain
|
sancus
:
data-review+
|
Details |
|
48 bytes,
text/x-phabricator-request
|
Details | Review |
The following Firefox probes will expire in the next major Firefox nightly release: version 88 [1].
WEBAUTHN_CREATE_CREDENTIAL_MS
WEBAUTHN_GET_ASSERTION_MS
security.webauthn_used
What to do about this:
- If one, some, or all of the metrics are no longer needed, please remove them from their definitions files (Histograms.json, Scalars.yaml, Events.yaml).
- If one, some, or all of the metrics are still required, please submit a Data Collection Review [2] and patch to extend their expiry. There is a shorter form for data collection renewal [3].
If you have any problems, please ask for help on the #data-help Slack channel or the #telemetry Matrix room at https://chat.mozilla.org/#/room/#telemetry:mozilla.org. We'll give you a hand.
Your Friendly, Neighborhood Telemetry Team
[1] https://wiki.mozilla.org/Release_Management/Calendar
[2] https://wiki.mozilla.org/Firefox/Data_Collection
[3] https://github.com/mozilla/data-review/blob/master/renewal_request.md
This is an automated message sent from probe-scraper. See https://github.com/mozilla/probe-scraper for details.
Comment 1•4 years ago
|
||
[Tracking Requested - why for this release]: dom/webauthn/tests/browser/browser_webauthn_telemetry.js depends on it.
Updated•4 years ago
|
Comment 2•4 years ago
|
||
Discussed with Martinho. He'll work on this right away to review the probes, ensure that they are still useful and then extend them.
| Assignee | ||
Comment 3•4 years ago
|
||
This is going to remain useful at least until we're happy with the updates in WebAuthn for 2021, particularly rollout on Android and CTAP2, so I'm extending out for a year.
| Assignee | ||
Comment 4•4 years ago
|
||
Updated•4 years ago
|
Comment 6•4 years ago
|
||
Comment on attachment 9202611 [details]
data-review
Load-balancing to :sancus
Comment 7•4 years ago
•
|
||
Comment on attachment 9202611 [details]
data-review
Considering the initial bug seems to pre-date the existing form, I've decided to fill in the full data review form to better document it. All the appropriate information is already available in the previous bug, just not formatted :)
Data Review Form:
- Is there or will there be documentation that describes the schema for the ultimate data set in a public, complete, and accurate way?
Yes, in the histogram and scalar definition files and in the probe dictionary.
- Is there a control mechanism that allows the user to turn the data collection on and off?
Yes, using standard Telemetry preferences.
- If the request is for permanent data collection, is there someone who will monitor the data over time?
Data collection expires in Firefox 100.
- 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”).
- 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/No)
Yes, :rmf or :neha will decide whether to renew after Firefox 100.
- Does the data collection use a third-party collection tool? If yes, escalate to legal.
No.
Data Renewal Form:
- Is the provided Data Collection Review complete, correct, and data-review+ by a Data Steward?
Yes.
- Is the data collection covered by the existing Firefox Privacy Notice?
Yes.
Comment 9•4 years ago
|
||
| bugherder | ||
Description
•