Closed
Bug 1623492
Opened 5 years ago
Closed 5 years ago
Report whether the OS compositor is being used in telemetry
Categories
(Core :: Graphics: WebRender, enhancement, P3)
Core
Graphics: WebRender
Tracking
()
RESOLVED
FIXED
mozilla76
People
(Reporter: jrmuizel, Assigned: jrmuizel)
Details
Attachments
(2 files)
47 bytes,
text/x-phabricator-request
|
jcristau
:
approval-mozilla-beta+
|
Details | Review |
2.27 KB,
text/plain
|
tdsmith
:
data-review+
|
Details |
No description provided.
Assignee | ||
Comment 1•5 years ago
|
||
Updated•5 years ago
|
Assignee: nobody → jmuizelaar
Status: NEW → ASSIGNED
Assignee | ||
Comment 2•5 years ago
|
||
Attachment #9134291 -
Flags: data-review?(tdsmith)
Comment 3•5 years ago
|
||
Comment on attachment 9134291 [details]
request.md
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 Scalars.yaml and the probe dictionary.
2) Is there a control mechanism that allows the user to turn the data collection on and off?
Yes, the Firefox telemetry opt-out.
3) If the request is for permanent data collection, is there someone who will monitor the data over time?
Yes, :jrmuizel.
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** (whether anonymous or otherwise; e.g., username, random IDs, etc. See the appendix for more details)?
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?
No, permanent collection.
9) Does the data collection use a third-party collection tool?
No.
Attachment #9134291 -
Flags: data-review?(tdsmith) → data-review+
Pushed by jmuizelaar@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/f985871b3e62
Expose OS compositor to telemetry.
Comment 5•5 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
status-firefox76:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla76
Assignee | ||
Comment 6•5 years ago
|
||
Comment on attachment 9134288 [details]
Bug 1623492. Expose OS compositor to telemetry.
Beta/Release Uplift Approval Request
- User impact if declined: We won't have visibility into our OS compositor usage in 75
- Is this code covered by automated tests?: No
- Has the fix been verified in Nightly?: No
- Needs manual test from QE?: No
- If yes, steps to reproduce:
- List of other uplifts needed: None
- Risk to taking this patch: Low
- Why is the change risky/not risky? (and alternatives if risky): Just adds some telemetry
- String changes made/needed:
Attachment #9134288 -
Flags: approval-mozilla-beta?
Updated•5 years ago
|
status-firefox75:
--- → affected
Comment 7•5 years ago
|
||
Comment on attachment 9134288 [details]
Bug 1623492. Expose OS compositor to telemetry.
add a telemetry scalar for WR, ok for 75.0b8
Attachment #9134288 -
Flags: approval-mozilla-beta? → approval-mozilla-beta+
Comment 8•5 years ago
|
||
bugherder uplift |
You need to log in
before you can comment on or make changes to this bug.
Description
•