Add telemetry probes to know WMF usage in chrome and content process
Categories
(Core :: Audio/Video: Playback, task, P1)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox87 | --- | fixed |
People
(Reporter: alwu, Assigned: alwu)
References
(Blocks 1 open bug)
Details
Attachments
(3 files)
|
(deleted),
text/x-phabricator-request
|
Details | |
|
(deleted),
text/x-phabricator-request
|
Details | |
|
(deleted),
text/plain
|
tdsmith
:
data-review+
|
Details |
Currently we would create WMF decoder module on different processes (chrome/content/rdd/gpu) and we would like to know the percentage of WMF usage for each process.
|
Assignee | |
Comment 1•4 years ago
|
||
Because we're not able to record telemetry from RDD process, so I changed my mind. Maybe we should record some data to know the percentage of using remote data decoder v.s. the percentage of using decoder in content/chrome process. Will file a new bug for that.
|
|
Assignee | |
Comment 2•4 years ago
|
||
Reopen this bug, because I still want to know how many users are still using WMF on content process, or on chrome process.
|
|
Assignee | |
Comment 3•4 years ago
|
||
|
|
Assignee | |
Comment 4•4 years ago
|
||
Depends on D103836
|
|
Assignee | |
Comment 5•4 years ago
|
||
|
||
Comment 6•4 years ago
|
||
Comment on attachment 9203519 [details]
data-review-request
The data-review is for a permanent collection but I see that it's set to expire in 93, which makes sense to me for this probe.
I left a comment on the diff that this could also be implemented equivalently as a simple (non-keyed) scalar, but that doesn't affect the data review.
--
- 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 probe definition files and the Probe Dictionary.
- Is there a control mechanism that allows the user to turn the data collection on and off?
Yes, the Firefox telemetry opt-out.
- If the request is for permanent data collection, is there someone who will monitor the data over time?
Yes, alwu.
- 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 data.
- Is the data collection request for default-on or default-off?
Default-on.
- 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.
- Is the data collection covered by the existing Firefox privacy notice?
Yes.
- Does there need to be a check-in in the future to determine whether to renew the data?
alwu et al are responsible for renewing the probe as needed.
- Does the data collection use a third-party collection tool?
No.
|
||
Comment 8•4 years ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/7713bebbfcd6
https://hg.mozilla.org/mozilla-central/rev/f6245e3daf66
|
|
Assignee | |
Updated•4 years ago
|
|
||
Updated•3 years ago
|
Description
•