Closed Bug 1754645 Opened 4 years ago Closed 3 years ago

Remove or update probes expiring in Firefox 100: MEDIA_RECORDER_*

Categories

(Core :: Audio/Video, task)

task

Tracking

()

RESOLVED FIXED
99 Branch
Tracking Status
firefox99 --- fixed

People

(Reporter: telemetry-probes, Assigned: bryce)

References

Details

(Whiteboard: [probe-expiry-alert])

Attachments

(3 files)

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

MEDIA_RECORDER_RECORDING_DURATION
MEDIA_RECORDER_TRACK_ENCODER_INIT_TIMEOUT_TYPE

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?(bvandyk)
  • MEDIA_RECORDER_TRACK_ENCODER_INIT_TIMEOUT_TYPE reports very low rates of timeouts, so seems safe to go.
  • MEDIA_RECORDER_RECORDING_DURATION is interesting still.

I'll remove the former and update the latter.

Assignee: nobody → bvandyk
Flags: needinfo?(bvandyk)

This probe reports when our different track encoders fail to init in the
MediaRecorder pipeline. The failure rates are very low, so I don't think keeping
this around is helping us.

Comment on attachment 9264885 [details]
renewal_request.md

This is fine, it looks like the original bug 1400757 doesn't have a data review form in it due to age, so I'm attaching that below:

Data Review Form:

  1. Is there or will there be documentation that describes the schema for the ultimate data set in a public, complete, and accurate way?

Yes, in the histogram definition files and in the probe dictionary.

  1. Is there a control mechanism that allows the user to turn the data collection on and off?

Yes, using standard Telemetry preferences.

  1. If the request is for permanent data collection, is there someone who will monitor the data over time?

Data collection expires in Firefox 112.

  1. Using the category system of data types on the Mozilla wiki, what collection type of data do the requested measurements fall under?

Category 2(“Interaction data”).

  1. Is the data collection request for default-on or default-off?

Default on for nightly and beta only.

  1. Does the instrumentation include the addition of any new identifiers (whether anonymous or otherwise; e.g., username, random IDs, etc. See the appendix for more details)?

No.

  1. Is the data collection covered by the existing Firefox privacy notice?

Yes.

  1. Does there need to be a check-in in the future to determine whether to renew the data? (Yes/No)

Yes, :bryce or :pehrsons will decide whether to renew or not.

  1. Does the data collection use a third-party collection tool? If yes, escalate to legal.

No.

Attachment #9264885 - Flags: data-review?(sancus) → data-review+
Pushed by bvandyk@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/a502c28e8d98 Remove MEDIA_RECORDER_TRACK_ENCODER_INIT_TIMEOUT_TYPE probe. r=padenot https://hg.mozilla.org/integration/autoland/rev/17ba69318293 Extend MEDIA_RECORDER_RECORDING_DURATION probe lifetime. r=padenot
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → 99 Branch
See Also: → 1811154
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: