Closed Bug 1811157 Opened 2 years ago Closed 2 years ago

Remove or update probes expiring in Firefox 112: media.video_h* before Gecko version gets increased to 112 on 2023-02-13

Categories

(Core :: Audio/Video: Playback, task)

task

Tracking

()

RESOLVED FIXED
112 Branch
Tracking Status
firefox-esr102 --- unaffected
firefox109 --- unaffected
firefox110 --- unaffected
firefox111 - wontfix
firefox112 + fixed

People

(Reporter: telemetry-probes, Assigned: alwu)

References

Details

(Whiteboard: [probe-expiry-alert])

Attachments

(3 files, 1 obsolete file)

The following Firefox probes will expire in the next major Firefox nightly release: version 112 [1].

media.video_hardware_decoding_support
media.video_hd_hardware_decoding_support

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.

This will cause a permanent test failure of dom/media/test/browser/browser_telemetry_video_hardware_decoding_support.js once the Gecko version got increased to 112 on 2023-02-13.

Paul, can you take care of this?

Flags: needinfo?(padenot)
Summary: Remove or update probes expiring in Firefox 112: media.video_h* → Remove or update probes expiring in Firefox 112: media.video_h* before Gecko version gets increased to 112 on 2023-02-13

Alastor, can you handle this? We probably want to keep those.

Flags: needinfo?(padenot) → needinfo?(alwu)

The bug is marked as tracked for firefox111 (nightly). We have limited time to fix this, the soft freeze is in a day. 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 auto_nag documentation.

Flags: needinfo?(jmathies)
Attachment #9317279 - Attachment description: WIP: Bug 1811157 - disable test for telemetry collected about video hardware decoding until probe gets extended → Bug 1811157 - disable test for telemetry collected about video hardware decoding until probe gets extended
Pushed by csabou@mozilla.com: https://hg.mozilla.org/mozilla-central/rev/d561ece0b43b disable test for telemetry collected about video hardware decoding until probe gets extended. a=test-only
Assignee: nobody → alwu
Flags: needinfo?(alwu)
Attached file renewal_request.md (obsolete) —
Attachment #9317437 - Flags: data-review?(chutten)

Comment on attachment 9317437 [details]
renewal_request.md

Sorry, it's not permitted to make an expiring collection permanent using the renewal form (as the short form is missing some information necessary for permanent collections). Please use the full form to request the permanent collection

Attachment #9317437 - Flags: data-review?(chutten) → data-review-
Attached file data-review-request
Attachment #9317437 - Attachment is obsolete: true
Attachment #9317750 - Flags: data-review?(chutten)
Flags: needinfo?(jmathies)

Comment on attachment 9317750 [details]
data-review-request

PRELIMINARY NOTES:
The answer to Q7 "How long will this data be collected?" for permanent collections must be of the form I want to permanently monitor this data. (put someone’s name here). The important piece is finding an individual responsible for the lifetime of this collection.

To avoid sending this back again, I will assume :alwu is taking responsibility. If you do not wish to, please find someone else who will or treat this as data-review-.

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, :alwu is 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+

Flags: needinfo?(alwu)
Attachment #9317750 - Flags: data-review?(chutten) → data-review+

Yes, I will take responsibility for those probes. Thank you.

Flags: needinfo?(alwu)
Pushed by alwu@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/f4b6eb6383d9 extend scalars to never expire. r=media-playback-reviewers,azebrowski
Status: NEW → RESOLVED
Closed: 2 years ago
Keywords: leave-open
Resolution: --- → FIXED
Target Milestone: --- → 112 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: