Closed Bug 1639283 Opened 3 months ago Closed 3 months ago

Add some Telemetry to measure how parts of the WebRTC screen / window sharing UI is being used

Categories

(Firefox :: Site Permissions, task)

task

Tracking

()

RESOLVED FIXED
Firefox 78
Tracking Status
firefox77 --- fixed
firefox78 --- fixed

People

(Reporter: mconley, Assigned: mconley)

References

Details

Attachments

(2 files)

Actual probes TBD, but I'll list them here when I have them.

We would like probes to:

  • Count how many times the user shares their window, browser window, or screen (different counts for each)
  • Count how many times the user opts-in to silencing notifications
  • Count how many times the user opts out of the tab switch warning
  • Count how many times the tab switch warning was shown during a window/screen sharing session

Heads up to chutten and johannh that this is coming down the pike - we're aiming to get this landed and uplifted into beta. I hope to have a review request up today.

Assignee: nobody → mconley
Status: NEW → ASSIGNED
Attached file Data review form
Attachment #9150577 - Flags: data-review?(chutten)
Attachment #9150577 - Flags: data-review?(chutten) → data-review?(mmccorquodale)
Attachment #9150574 - Attachment description: Bug 1639283 - Add Telemetry to some of our WebRTC UI. r?pbz!, data-review=chutten → Bug 1639283 - Add Telemetry to some of our WebRTC UI. r?pbz!, data-review=mmccorquodale
Comment on attachment 9150577 [details]
Data review form

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, this will be documented in the probe dictionary. 

2.    Is there a control mechanism that allows the user to turn the data collection on and off?
Yes, users can opt out of telemetry collection.

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

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, Interaction data.

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?
No new identifiers. (The "ID" created is not a user/device identifier but for differentiating between unique sessions.)

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? 
Yes, check in at Firefox 82. 

9.    Does the data collection use a third-party collection tool? 
No. 

------
data-review +
Attachment #9150577 - Flags: data-review?(mmccorquodale) → data-review+

Putting this on your radar pascal - modulo any serious bugs that QA finds that we need to patch at the last minute, this should be the last chunk that'll need uplift.

Today is a bank holiday in Europe, putting Ryan in the loop in case there is a last uplift request here.

Comment on attachment 9150574 [details]
Bug 1639283 - Add Telemetry to some of our WebRTC UI. r?pbz!, data-review=mmccorquodale

Beta/Release Uplift Approval Request

  • User impact if declined: None.
  • Is this code covered by automated tests?: No
  • Has the fix been verified in Nightly?: Yes
  • 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): Pretty passive patch that adds some Telemetry probes.
  • String changes made/needed: None.
Attachment #9150574 - Flags: approval-mozilla-beta?
Group: mozilla-employee-confidential

Comment on attachment 9150574 [details]
Bug 1639283 - Add Telemetry to some of our WebRTC UI. r?pbz!, data-review=mmccorquodale

Adds more Telemetry probes for the WebRTC UI changes landing in 77. Approved for 77.0b9.

Attachment #9150574 - Flags: approval-mozilla-beta? → approval-mozilla-beta+
See Also: → 1656127
You need to log in before you can comment on or make changes to this bug.