Remove or update metrics expiring in Firefox 126: rtcrtpsender.* before Gecko version gets increased to 126 on 2024-03-18
Categories
(Core :: WebRTC: Signaling, task)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr115 | --- | unaffected |
| firefox123 | --- | unaffected |
| firefox124 | --- | unaffected |
| firefox125 | + | fixed |
People
(Reporter: telemetry-probes, Assigned: bwc)
References
Details
(Whiteboard: [metric-expiry-alert])
Attachments
(2 files)
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
383 bytes,
text/plain
|
travis_
:
data-review+
|
Details |
The following metrics will expire in the next Firefox Nightly release: version 126.
rtcrtpsender.count
rtcrtpsender.count_setparameters_compat
rtcrtpsender.setparameters.blame_length_changed
rtcrtpsender.setparameters.blame_no_getparameters
rtcrtpsender.setparameters.blame_no_transactionid
rtcrtpsender.setparameters.fail_length_changed
rtcrtpsender.setparameters.fail_no_encodings
rtcrtpsender.setparameters.fail_no_getparameters
rtcrtpsender.setparameters.fail_no_transactionid
rtcrtpsender.setparameters.fail_other
rtcrtpsender.setparameters.fail_rid_changed
rtcrtpsender.setparameters.fail_stale_transactionid
rtcrtpsender.setparameters.warn_length_changed
rtcrtpsender.setparameters.warn_no_getparameters
rtcrtpsender.setparameters.warn_no_transactionid
rtcrtpsender.used_sendencodings
What to do about this:
- If one, some, or all of the metrics are no longer needed, please remove them from their
metrics.yamldefinition file. - If one, some, or all of the metrics are still required, please submit a Data Collection Review and patch to extend their expiry. There is a shorter form for data collection renewal.
If you have any problems, please ask for help on the #glean Matrix room or the #data-help Slack channel.
We'll give you a hand.
Your Friendly Neighbourhood Glean Team
This bug was auto-filed by probe-scraper.
Comment 1•2 years ago
|
||
Tracking because at least dom/media/webrtc/tests/mochitests/test_peerConnection_scaleResolution_oldSetParameters.html checks for this.
Updated•2 years ago
|
Comment 2•2 years ago
|
||
The bug is marked as tracked for firefox125 (nightly). However, the bug still isn't assigned.
:jimm, could you please find an assignee for this tracked bug? If you disagree with the tracking decision, please talk with the release managers.
For more information, please visit BugBot documentation.
| Assignee | ||
Comment 3•2 years ago
|
||
I think we're going to need to extend this again, although if Google Meet can fix their code we should be most of the way there.
| Assignee | ||
Updated•2 years ago
|
Updated•2 years ago
|
| Assignee | ||
Comment 4•2 years ago
|
||
| Assignee | ||
Comment 5•2 years ago
|
||
Comment 6•2 years ago
•
|
||
Comment on attachment 9390189 [details]
data-review-1881403.md
Data Collection Renewal Review
- Is the provided Data Collection Review complete, correct, and data-review+ by a Data Steward?
yes
- Is the data collection covered by the existing Firefox Privacy Notice?
yes
Result
data-review+
(P.S. this is one of the best answers I've seen for why the initial period was insufficient! I laughed out when reading it :) )
Description
•