1749884 - Remove or update probes expiring in Firefox 99: TLS_1_3_CLIENT_AUTH_USES_PHA

Status: RESOLVED FIXED

(Core :: Security: PSM, task, P1)

Description

[telemetry-probes]

The following Firefox probes will expire in the next major Firefox nightly release: version 99 [1].

TLS_1_3_CLIENT_AUTH_USES_PHA

What to do about this:

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

[BugBot [:suhaib / :marco]]

Redirect a needinfo that is pending on an inactive user to the triage owner.
:keeler, since the bug has recent activity, could you have a look please?

For more information, please visit auto_nag documentation.

Comment 2

[Dana Keeler (she/her) [:keeler]]

Attachment: request.md

Comment 3

[Dana Keeler (she/her) [:keeler]]

Attachment: Bug 1749884 - remove expired client auth cert telemetry and add new permanent telemetry r?rmf

Comment 4

[Jared Hirsch [:jhirsch] (he/him) (Needinfo please)]

Comment on attachment 9283746 [details]
request.md

data-review+

Data Review Form (to be filled by Data Stewards)

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 Telemetry definitions files Histograms.json, Scalars.yaml, and/or Events.yaml and in the Probe Dictionary at https://probes.telemetry.mozilla.org.

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, the usual telemetry opt-out controls.

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

Yes.

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.

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?

No.

Comment 5

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/1d13b6732f98
remove expired client auth cert telemetry and add new permanent telemetry r=rmf

Comment 6

[Cristian Tuns]

https://hg.mozilla.org/mozilla-central/rev/1d13b6732f98