Collect Linux back end telemetry data
Categories
(Core :: Graphics, enhancement)
Tracking
()
Tracking | Status | |
---|---|---|
firefox82 | --- | fixed |
People
(Reporter: stransky, Assigned: mkaply)
References
Details
Attachments
(2 files, 1 obsolete file)
(deleted),
text/plain
|
chutten
:
data-review+
|
Details |
(deleted),
text/x-phabricator-request
|
Details |
Collect Linux back end telemetry data (Wayland/X11) to better plan Linux development.
It's at about:support, "Window Protocol" and can be "Wayland", "Wayland/drm", "x11" for now.
Comment 1•4 years ago
|
||
Data collections are usually implemented by the components doing the collection. Looks like Core:Graphics is the right place to do that. In bug 1554540 it was added to about:support.
Comment 2•4 years ago
|
||
https://searchfox.org/mozilla-central/rev/25d491b7924493b5d4bedc07841a1cd92f271100/toolkit/content/aboutSupport.js#603-604
Please include windowProtocol and, if possible, desktopEnvironment in crash reports as well.
Updated•4 years ago
|
Assignee | ||
Comment 3•4 years ago
|
||
Here's the process for this.
https://wiki.mozilla.org/Firefox/Data_Collection
We'll need to do a data collection request. I'll own working on that.
Assignee | ||
Comment 4•4 years ago
|
||
Assignee | ||
Updated•4 years ago
|
Assignee | ||
Updated•4 years ago
|
Comment 5•4 years ago
|
||
Assignee | ||
Comment 6•4 years ago
|
||
I think this is right...
Comment 7•4 years ago
|
||
Assignee | ||
Comment 8•4 years ago
|
||
crash report annotation is here:
https://searchfox.org/mozilla-central/source/widget/GfxInfoX11.cpp#55
I think I can add telemetry here:
https://searchfox.org/mozilla-central/source/widget/GfxInfoX11.cpp#693
any advice on where to put this chutten? I guess I'm looking for something that only happens once.
Most of this is called from FindBlocklistedDeviceInList. I have no idea how often that gets called.
Martin, is this something one of your team can take on? We have permission to do it now and I can help with getting the code together, just don't know where to put it.
Comment 9•4 years ago
|
||
I'm afraid I don't know gfx code all that well, so I can't point to any place that's called once. (and then to find one that also has easy access to the backend name). But when you do, I presume you're planning on stuffing it in a String Scalar? You won't have any problems accessing that from wherever you are (even if you have to do it from inside the gpu process)
Reporter | ||
Comment 10•4 years ago
|
||
(In reply to Mike Kaply [:mkaply] from comment #8)
https://searchfox.org/mozilla-central/source/widget/GfxInfoX11.cpp#693
any advice on where to put this chutten? I guess I'm looking for something that only happens once.
Most of this is called from FindBlocklistedDeviceInList. I have no idea how often that gets called.
Martin, is this something one of your team can take on? We have permission to do it now and I can help with getting the code together, just don't know where to put it.
https://searchfox.org/mozilla-central/source/widget/GfxInfoX11.cpp#693 is a good place, it's called only once after Firefox start.
Yes, I can review/create the patch if you give me some hints how to export the data.
Thanks.
Assignee | ||
Comment 11•4 years ago
|
||
Assignee | ||
Comment 12•4 years ago
|
||
Martin: I think this patch will do it.
The way to test is to build and then start Firefox and go to about:telemetry.
Search on LINUX_WINDOW_PROTOCOL or Wayland and hopefully you'll see something.
Reporter | ||
Comment 13•4 years ago
|
||
(In reply to Mike Kaply [:mkaply] from comment #12)
Martin: I think this patch will do it.
The way to test is to build and then start Firefox and go to about:telemetry.
Search on LINUX_WINDOW_PROTOCOL or Wayland and hopefully you'll see something.
Yes, I do see 'gfx.linux_window_protocol' is 'wayland/drm' in my case.
Updated•4 years ago
|
Comment 14•4 years ago
|
||
Comment 15•4 years ago
|
||
bugherder |
Description
•