Closed
Bug 1532391
Opened 6 years ago
Closed 6 years ago
Extend lifetime of MEDIA_RECORDER_RECORDING_DURATION, MEDIA_RECORDER_TRACK_ENCODER_INIT_TIMEOUT_TYPE, and SCALARS_MEDIARECORDER.RECORDING_COUNT telemetry probes
Categories
(Core :: Audio/Video: Recording, enhancement, P3)
Core
Audio/Video: Recording
Tracking
()
RESOLVED
FIXED
mozilla68
Tracking | Status | |
---|---|---|
firefox68 | --- | fixed |
People
(Reporter: bryce, Assigned: bryce)
References
Details
Attachments
(2 files)
3.68 KB,
text/plain
|
tdsmith
:
data-review+
|
Details |
47 bytes,
text/x-phabricator-request
|
Details | Review |
As with previous extensions of these probes (bug 1429765, bug 1480589), I'd like to extend these further as the information remains useful to the media team for guiding resource allocation.
Assignee | ||
Comment 1•6 years ago
|
||
Could the data reviewer please advise what review is appropriate for updating scalars and histogram files for this extension? Is further review required outside of that above data review if I'm bumping a version number?
Attachment #9049520 -
Flags: data-review?
Assignee | ||
Comment 2•6 years ago
|
||
Assignee | ||
Updated•6 years ago
|
Attachment #9049520 -
Flags: data-review? → data-review?(teon)
Assignee | ||
Updated•6 years ago
|
Attachment #9049520 -
Flags: data-review?(teon) → data-review?(tdsmith)
Comment 3•6 years ago
|
||
Comment on attachment 9049520 [details]
DataReviewRequest.md
data-review+
> Could the data reviewer please advise what review is appropriate for updating scalars and histogram files for this extension? Is further review required outside of that above data review if I'm bumping a version number?
The usual code review policy applies to changes to the scalar and histogram definitions. The code reviewer may optionally be a Telemetry module peer, but does not have to be.
--
1) Is there or will there be **documentation** that describes the schema for the ultimate data set available publicly, complete and accurate?
Yes, in Histograms.json, Scalars.yaml, and the probe dictionary.
2) Is there a control mechanism that allows the user to turn the data collection on and off? Provide details as to the control mechanism available.
Yes, the opt-out in the Firefox preferences.
3) If the request is for permanent data collection, is there someone who will monitor the data over time?
N/A; temporary collection.
4) Using the **[category system of data types](https://wiki.mozilla.org/Firefox/Data_Collection)** on the Mozilla wiki, what collection type of data do the requested measurements fall under?
Category 1, technical data.
5) Is the data collection request for default-on or default-off?
Default-on.
6) Does the instrumentation include the addition of **any *new* identifiers**?
No.
7) Is the data collection covered by the existing Firefox privacy notice?
Yes.
8) Does there need to be a check-in in the future to determine whether to renew the data?
Yes; Bryce is responsible for deciding to renew the collection before it expires in 72 if it’s still needed.
9) Does the data collection use a third-party collection tool?
No.
Attachment #9049520 -
Flags: data-review?(tdsmith) → data-review+
Pushed by bvandyk@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/1a940d2db42b
Extend MediaRecorder telemetry probes until 72. r=drno
Comment 5•6 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 6 years ago
status-firefox68:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla68
You need to log in
before you can comment on or make changes to this bug.
Description
•