Closed Bug 1813593 Opened 4 months ago Closed 4 months ago

Make use counter data available locally

Categories

(Core :: General, enhancement)

Product:
Core
Component:
General
Type:
enhancement

Tracking

()

Status:
RESOLVED FIXED
Milestone:
111 Branch
Tracking Flags:
Tracking Status
firefox111 --- fixed

People

(Reporter: zcorpan, Assigned: emilio)

References

Details

Attachments

(1 file)

Bug 1813593 - Dump use counters with dom.use_counters.dump.{document,worker,page}. r=smaug
48 bytes, text/x-phabricator-request
Details | Review

Dump the use counter data of a run to stderr behind a pref or something around those lines, so that it's possible to collect use counter data locally. The idea is to make it possible to get Firefox use counter data into httparchive, which should help with web compat analysis.

Flags: needinfo?(emilio)

Should the counters be associated with an individual top level page or document, or just aggregate for the entire process lifetime? I had previously discussed something similar with Smaug who pointed me at https://searchfox.org/mozilla-central/rev/ed02e6e84e433cd283e86377524462b4e8b1597b/dom/base/Document.cpp#15582 and https://searchfox.org/mozilla-central/rev/ed02e6e84e433cd283e86377524462b4e8b1597b/dom/workers/WorkerPrivate.cpp#4285 as relevant places that would need tweaking to do something like this outside of Telemetry.

Also it'd be worth understanding a bit better how webpagetest currently extracts chrome feature usage - both the semantics of things like Comment 1 and logistically what kind of file / format it's exporting to, to make sure it'd be reasonable to ingest and expose for something like http archive. On the latter point my suspicion is that it's part of a larger trace file processed here https://github.com/WPO-Foundation/wptagent/blob/eca6d1825f2b8d12bd14ea83134318f682eed903/internal/support/trace_parser.py#L899

Ok, so this is not just the UI about:telemetry#histograms-tab_search=use_counter2
but actually get the data dumped somewhere.

Assignee: nobody → emilio
Flags: needinfo?(emilio)

The idea is that dumping the counter with the url all the time prevents
(or at least mitigates) races between different process.

This should allow to get the counters from local builds in a
semi-structured / easy to filter-and-parse way.

Simon, lmk if the format in comment 4 works for you?

Flags: needinfo?(zcorpan)
Attachment #9315238 - Attachment description: Bug 1813593 - Dump use counters with dom.use_counters.dump. r=smaug → Bug 1813593 - Dump use counters with dom.use_counters.dump.{document,worker,page}. r=smaug
Pushed by ealvarez@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/299912be733e
Dump use counters with dom.use_counters.dump.{document,worker,page}. r=smaug,zcorpan

https://hg.mozilla.org/mozilla-central/rev/299912be733e

Status: NEW → RESOLVED
Closed: 4 months ago
status-firefox111: affected → fixed
Resolution: --- → FIXED
Target Milestone: --- → 111 Branch
Flags: needinfo?(zcorpan)
You need to log in before you can comment on or make changes to this bug.