Closed Bug 1873394 Opened 4 months ago Closed 3 months ago

[wmfme] create telemetry probes to collect playback data for MFCDM

Categories

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

task

Tracking

()

RESOLVED FIXED
124 Branch
Tracking Status
firefox124 --- fixed

People

(Reporter: alwu, Assigned: alwu)

References

(Blocks 1 open bug)

Details

Attachments

(4 files, 3 obsolete files)

We want to add some probes to understand whether MFCDM is working well.

Attachment #9371905 - Attachment description: WIP: Bug 1873394 - part1 : collect playback statistic data for MFCDM. → Bug 1873394 - part1 : collect playback statistic data for MFCDM.
Attachment #9371906 - Attachment description: WIP: Bug 1873394 - part2 : add telemetry probe to record error and crash. → Bug 1873394 - part2 : add telemetry probe to record error and crash.

When enaling the media engine playback, we would always start with using
the external state machine. Then fallback to the normal state machine if
the conditions are not met, eg. only enable encrypted media playback, or
the codec types/key system types which the media engine doesn't support.

This kind of transistion should be smooth and always succeed. If not,
then it would probably cause bad effect on the user experience, so we
add the probes to measure the error rate.

Depends on D198110

Attached file data-review-request (obsolete) —
Attachment #9372191 - Flags: data-review?(chutten)

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

PRELIMINARY NOTES:

For future reviews, please provide full information of what data is collected along with the events. In this case I read the code and the extra keys are a bunch of technical information like codecs and stuff that are no worse than Cat2.

(( Since I popped over to the code review and already suggested Glean, I feel I should also note here that Glean-defined data collections can use ./mach data-review to generate the data collection review request template for you. Just another little nicety that Glean's set up to provide. Oh, and if you choose to switch from Telemetry to Glean (or using Glean and GIFFT to collect to both Glean and Telemetry), there's no need for a new data collection review -- this one will suffice. You'll notice that there are no questions specific to the mechanism you're using to collect the data, so long as they're mozilla-controlled. ))

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 the product's preferences.

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

Yes, Alastor Wu 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 2, Interaction.

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+

Attachment #9372191 - Flags: data-review?(chutten) → data-review+
Attachment #9372176 - Attachment description: Bug 1873394 - part3 : record telemetry for recreating the state machine. → Bug 1873394 - part3 : record telemetry for the failure to recreate the state machine.
Attached file data-review-request

Update a new data review, because I changed the probe in my new patches.

Attachment #9372191 - Attachment is obsolete: true
Attachment #9378046 - Flags: data-review?(chutten)

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

PRELIMINARY NOTES:
That's an interesting mix of ./mach data-review and plain template in your request.

The answer to Q6 should point to the Glean Dictionary, where all Glean data is documented in full.

The answer to Q8 should be "These collections are Glean. The opt-out can be found in the product's preferences."

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 the product's preferences.

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

No. This collection will expire in Firefox 130.

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+

Attachment #9378046 - Flags: data-review?(chutten) → data-review+
Pushed by alwu@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/44fdf4e83c7c
part1 : collect playback statistic data for MFCDM. r=media-playback-reviewers,chunmin,chutten
https://hg.mozilla.org/integration/autoland/rev/6711b73d58e1
part2 : add telemetry probe to record error and crash. r=jolin,chutten
https://hg.mozilla.org/integration/autoland/rev/b355f33d28c9
part3 : record telemetry for the failure to recreate the state machine. r=jolin,chutten
Regressions: 1879250
Status: RESOLVED → REOPENED
Flags: needinfo?(alwu)
Resolution: FIXED → ---
Target Milestone: 124 Branch → ---

Backed out changeset b355f33d28c9 (bug 1873394)
Backed out changeset 6711b73d58e1 (bug 1873394)
Backed out changeset 44fdf4e83c7c (bug 1873394)

Backed out changeset b355f33d28c9 (bug 1873394)
Backed out changeset 6711b73d58e1 (bug 1873394)
Backed out changeset 44fdf4e83c7c (bug 1873394)

Attachment #9378970 - Attachment is obsolete: true
Flags: needinfo?(alwu)
Pushed by alwu@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/bbe965b583e3
part1 : collect playback statistic data for MFCDM. r=media-playback-reviewers,chunmin,chutten
https://hg.mozilla.org/integration/autoland/rev/a7fbe977109f
part2 : add telemetry probe to record error and crash. r=jolin,chutten
https://hg.mozilla.org/integration/autoland/rev/89318af79fc6
part3 : record telemetry for the failure to recreate the state machine. r=jolin,chutten
Attachment #9378971 - Attachment is obsolete: true
Status: REOPENED → RESOLVED
Closed: 3 months ago3 months ago
Resolution: --- → FIXED
Target Milestone: --- → 124 Branch
Blocks: 1881589
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: