Remove or update probes expiring in Firefox 102: OPAQUE_RESPONSE_BLOCKING* before Gecko version increases to 102 on 2022-05-02
Categories
(Core :: DOM: Networking, task, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr91 | --- | unaffected |
firefox99 | --- | unaffected |
firefox100 | --- | unaffected |
firefox101 | + | fixed |
People
(Reporter: telemetry-probes, Assigned: farre)
References
Details
(Whiteboard: [probe-expiry-alert][necko-triaged])
Attachments
(1 file)
The following Firefox probes will expire in the next major Firefox nightly release: version 102 [1].
OPAQUE_RESPONSE_BLOCKING_TIME_MS
OPAQUE_RESPONSE_BLOCKING
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•2 years ago
|
||
Andreas, heya, two questions for you:
- What do you think? I suspect we have enough data to know we want to proceed and to get more meaningful metrics we need to have an updated implementation and start enforcing parts of the network filter.
- Are you willing to take this if you agree on removal?
Comment 2•2 years ago
|
||
Tracking because this has a test netwerk/test/browser/browser_opaque_response_blocking_telemetry.js
Assignee | ||
Comment 3•2 years ago
|
||
Sounds reasonable, we would need new probes in any case I guess.
Updated•2 years ago
|
Comment 4•2 years ago
|
||
Just a reminder that the version bump is coming on Monday, so we'll need a patch for this soon.
Assignee | ||
Comment 5•2 years ago
|
||
Updated•2 years ago
|
Pushed by afarre@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/5d44356db349 Remove OPAQUE_RESPONSE_BLOCKING* probes. r=necko-reviewers,kershaw
Comment 7•2 years ago
|
||
Backed out for causing build bustages.
Backout link: https://hg.mozilla.org/integration/autoland/rev/2134212765b907a4c37c4e082bf5adf2816e8029
Push with failures: https://treeherder.mozilla.org/jobs?repo=autoland&resultStatus=testfailed%2Cbusted%2Cexception%2Cretry%2Cusercancel&revision=5d44356db349c073cdb7453b1200f7b9f0a68498
Failure log: https://treeherder.mozilla.org/logviewer?job_id=376254069&repo=autoland&lineNumber=1231
Updated•2 years ago
|
Updated•2 years ago
|
Pushed by archaeopteryx@coole-files.de: https://hg.mozilla.org/integration/autoland/rev/bca722f2f0b0 Remove OPAQUE_RESPONSE_BLOCKING* probes. r=necko-reviewers,kershaw
Comment 9•2 years ago
|
||
bugherder |
Assignee | ||
Updated•2 years ago
|
Description
•