Collect Telemetry to compare success rate of regular image, video, audio loads and upgraded image, video, audio loads
Categories
(Core :: DOM: Security, task, P3)
Tracking
()
People
(Reporter: ckerschb, Assigned: ckerschb)
References
(Blocks 1 open bug)
Details
(Whiteboard: [domsecurity-active])
Attachments
(2 files, 2 obsolete files)
3.09 KB,
text/plain
|
chutten
:
data-review+
|
Details |
48 bytes,
text/x-phabricator-request
|
dmeehan
:
approval-mozilla-release+
|
Details | Review |
Assignee | ||
Updated•1 year ago
|
Assignee | ||
Updated•1 year ago
|
Assignee | ||
Comment 1•1 year ago
|
||
Updated•1 year ago
|
Assignee | ||
Comment 3•1 year ago
|
||
Assignee | ||
Comment 4•1 year ago
|
||
Comment on attachment 9320284 [details]
Bug 1819336: Collect Telemetry to compare success rate of regular image loads and upgraded image loads, r=freddyb
Beta/Release Uplift Approval Request
- User impact if declined: No user impact. This patch is just collecting telemetry for image failure rates in regular browsing mode and auto-upgrading mode (http to https) because we want to run a study.
- Is this code covered by automated tests?: No
- 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): It's just an if-else branch check for collecting telemetry.
- String changes made/needed: no
- Is Android affected?: Yes
Assignee | ||
Updated•1 year ago
|
Assignee | ||
Updated•1 year ago
|
Assignee | ||
Updated•1 year ago
|
Assignee | ||
Comment 5•1 year ago
|
||
Assignee | ||
Comment 6•1 year ago
|
||
Assignee | ||
Updated•1 year ago
|
Assignee | ||
Updated•1 year ago
|
Comment 7•1 year ago
|
||
Comment on attachment 9320764 [details]
data-review-1819336.txt
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.
Is there a control mechanism that allows the user to turn the data collection on and off?
Yes. This collection 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?
Yes, ckerschbaumer and freddyb are responsible.
Using the category system of data types on the Mozilla wiki, what collection type of data do the requested measurements fall under?
Category 1, Technical.
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 the data collection use a third-party collection tool?
No.
Result: datareview+
Pushed by mozilla@christophkerschbaumer.com: https://hg.mozilla.org/integration/autoland/rev/9a955a5bcfc2 Collect Telemetry to compare success rate of regular image, video, audio loads and upgraded image, video, audio loads, r=freddyb
Comment 9•1 year ago
|
||
bugherder |
Comment 10•1 year ago
|
||
Comment on attachment 9320771 [details]
Bug 1819336: Collect Telemetry to compare success rate of regular image, video, audio loads and upgraded image, video, audio loads, r=freddyb
Beta/Release Uplift Approval Request
- User impact if declined: No user impact. This patch is just collecting telemetry for failure rates in regular browsing mode and auto-upgrading mode (http to https) because we want to run a study that requires flipping a pref and this new telemetry probe.
- 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): It's just an if-else branch check for collecting telemetry.
- String changes made/needed: None
- Is Android affected?: Yes
Comment 11•1 year ago
|
||
Comment on attachment 9320771 [details]
Bug 1819336: Collect Telemetry to compare success rate of regular image, video, audio loads and upgraded image, video, audio loads, r=freddyb
Clearing the beta request flag, this patch landed in 112 which merges to beta today.
Comment hidden (obsolete) |
Comment 13•1 year ago
|
||
As much as I would like that to be true, I won't believe that adding a new telemetry probe will cause a performance improvement.
Comment 14•1 year ago
|
||
(In reply to Frederik Braun [:freddy] from comment #13)
As much as I would like that to be true, I won't believe that adding a new telemetry probe will cause a performance improvement.
Hi Frederik! Sorry for the confusion, it seems I pasted the alert summary on the wrong culprit. I marked the comment as obsolete. Thanks for the ni!
Comment 15•1 year ago
|
||
Comment on attachment 9320771 [details]
Bug 1819336: Collect Telemetry to compare success rate of regular image, video, audio loads and upgraded image, video, audio loads, r=freddyb
Approved for 111.0.1
Comment 16•1 year ago
|
||
bugherder uplift |
Description
•