Closed Bug 1484255 Opened Last year Closed Last year

Telemetry for new certificate error pages

Categories

(Firefox :: Security, enhancement, P1)

enhancement

Tracking

()

RESOLVED FIXED
Firefox 64
Tracking Status
firefox64 --- fixed

People

(Reporter: johannh, Assigned: johannh)

References

Details

Attachments

(2 files)

We'd like to measure user interaction with the new certificate error pages. We collected a number of possible measurements/improvements here: https://docs.google.com/document/d/1aEEqg42ksMGpHNNfEDK8p1rxMHyaV23s3kZzwA21g5c/edit#

We definitely want to get rid of using the old SECURITY_UI probe (https://mzl.la/2JEwAlH).
Assignee: nobody → jhofmann
Status: NEW → ASSIGNED
Priority: P2 → P1
Attached file request.md
Attachment #9016037 - Flags: review?(francois)
Comment on attachment 9016037 [details]
request.md

1) Is there or will there be **documentation** that describes the schema for the ultimate data set available publicly, complete and accurate?

Yes, in Events.yaml.

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

Yes, telemetry setting.

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

Not permanent.

4) Using the **[category system of data types](https://wiki.mozilla.org/Firefox/Data_Collection)** on the Mozilla wiki, what collection type of data do the requested measurements fall under?  **

Category 1 and 2.

5) Is the data collection request for default-on or default-off?

Default ON, only in pre-release channels.

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 there need to be a check-in in the future to determine whether to renew the data?

No, telemetry alerts are enough.
Attachment #9016037 - Flags: review?(francois) → review+
Chris, this is a new Event probe, but I assume it's fine because it's only sent when users encounter a TLS certificate error page.
Tied to user interaction means I'm not too worried about volume. And it's prerelease-only.
Pushed by jhofmann@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/1119f9458b5d
Add Telemetry Events for the certificate error pages. r=nhnt11,keeler
Backout by aciure@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/111455f16f4b
Backed out changeset 1119f9458b5d for browser_aboutCertError_telemetry.js failures CLOSED TREE
Attachment #9016036 - Attachment description: Bug 1484255 - Add Telemetry Events for the certificate error pages. r=nhnt11,keeler,chutten → Bug 1484255 - Add Telemetry Events for the certificate error pages. r=nhnt11,keeler
Pushed by jhofmann@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/00562394d243
Add Telemetry Events for the certificate error pages. r=nhnt11,keeler
Flags: needinfo?(jhofmann)
https://hg.mozilla.org/mozilla-central/rev/00562394d243
Status: ASSIGNED → RESOLVED
Closed: Last year
Resolution: --- → FIXED
Target Milestone: --- → Firefox 64
Depends on: 1500103
Build ID 	20181023100120
User Agent 	Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:65.0) Gecko/20100101 Firefox/65.0

Verified in latest Nightly
Regressions: 1558872
You need to log in before you can comment on or make changes to this bug.