Remove or update metrics expiring in Firefox 135: webrtcdtls.* before Gecko version gets increase to 135 on 2024-11-25
Categories
(Core :: WebRTC, task)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr115 | --- | unaffected |
| firefox-esr128 | --- | unaffected |
| firefox132 | --- | unaffected |
| firefox133 | --- | unaffected |
| firefox134 | + | fixed |
People
(Reporter: telemetry-probes, Assigned: anna.weine)
References
Details
(Whiteboard: [metric-expiry-alert])
Attachments
(1 file)
The following metrics will expire in the next Firefox Nightly release: version 135.
webrtcdtls.cipher
webrtcdtls.client_handshake_result
webrtcdtls.protocol_version
webrtcdtls.server_handshake_result
webrtcdtls.srtp_cipher
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 patch to extend their expiry.
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.
| Assignee | ||
Comment 1•1 year ago
|
||
I would prolong the use of the telemetry probes: as there is no active use of DTLS1.3, we need to make sure that when actors will start using it, we are capable of catching any problems.
Comment 2•1 year ago
|
||
Tracking because dom/media/webrtc/tests/mochitests/test_peerConnection_glean.html checks for this.
Comment 3•1 year ago
|
||
The bug is marked as tracked for firefox134 (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.
Comment 4•1 year ago
|
||
This is a reminder regarding comment #3!
The bug is marked as tracked for firefox134 (nightly). We have limited time to fix this, the soft freeze is in 10 days. However, the bug still isn't assigned.
Comment 5•1 year ago
|
||
Reminder: This needs to be resolved this week.
Comment 6•1 year ago
|
||
This is a reminder regarding comment #3!
The bug is marked as tracked for firefox134 (nightly). We have limited time to fix this, the soft freeze is in 3 days. However, the bug still isn't assigned.
| Assignee | ||
Comment 7•1 year ago
|
||
Updated•1 year ago
|
Updated•1 year ago
|
Updated•11 months ago
|
Description
•