Closed Bug 1763527 Opened 2 years ago Closed 2 years ago

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)

task

Tracking

()

RESOLVED FIXED
101 Branch
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:

  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.

Flags: needinfo?(annevk)

Andreas, heya, two questions for you:

  1. 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.
  2. Are you willing to take this if you agree on removal?
Flags: needinfo?(annevk) → needinfo?(afarre)

Tracking because this has a test netwerk/test/browser/browser_opaque_response_blocking_telemetry.js

Summary: Remove or update probes expiring in Firefox 102: OPAQUE_RESPONSE_BLOCKING* → Remove or update probes expiring in Firefox 102: OPAQUE_RESPONSE_BLOCKING* before Gecko version increases to 102 on 2022-05-02

Sounds reasonable, we would need new probes in any case I guess.

Assignee: nobody → afarre
Flags: needinfo?(afarre)
Severity: -- → N/A
Priority: -- → P2
Whiteboard: [probe-expiry-alert] → [probe-expiry-alert][necko-triaged]

Just a reminder that the version bump is coming on Monday, so we'll need a patch for this soon.

Attachment #9274001 - Attachment description: WIP: Bug 1763527 - Remove OPAQUE_RESPONSE_BLOCKING* probes. → Bug 1763527 - Remove OPAQUE_RESPONSE_BLOCKING* probes.
Pushed by afarre@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/5d44356db349
Remove OPAQUE_RESPONSE_BLOCKING* probes. r=necko-reviewers,kershaw
Attachment #9274001 - Attachment description: Bug 1763527 - Remove OPAQUE_RESPONSE_BLOCKING* probes. → WIP: Bug 1763527 - Remove OPAQUE_RESPONSE_BLOCKING* probes.
Attachment #9274001 - Attachment description: WIP: Bug 1763527 - Remove OPAQUE_RESPONSE_BLOCKING* probes. → Bug 1763527 - Remove OPAQUE_RESPONSE_BLOCKING* probes.
Pushed by archaeopteryx@coole-files.de:
https://hg.mozilla.org/integration/autoland/rev/bca722f2f0b0
Remove OPAQUE_RESPONSE_BLOCKING* probes. r=necko-reviewers,kershaw
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 101 Branch
Flags: needinfo?(afarre)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: