Expose blink use counters to tracing |
||
Issue descriptionThe use counters are only reported in histograms currently which makes scraping and collecting them particularly difficult and error-prone. Exposing them as trace events would make it much easier to collect both in a dev environment and testing and would allow for synchronizing with the rest of the trace events which could be used for things like attribution (which css file caused this feature to be triggered, etc). In the short-term this would really help the HTTP Archive and make it possible to collect blink feature usage across the crawls but I expect it would also be useful for lighthouse.
,
Aug 11 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/720d2fb5ad67e08d11b926b255086579a3bd4b39 commit 720d2fb5ad67e08d11b926b255086579a3bd4b39 Author: pmeenan <pmeenan@chromium.org> Date: Thu Aug 11 16:04:10 2016 Added trace events for blink feature usage This adds a new trace category (blink.feature_usage) where trace events are generated each time a feature use counter is updated. BUG= 633644 Review-Url: https://codereview.chromium.org/2203913002 Cr-Commit-Position: refs/heads/master@{#411343} [modify] https://crrev.com/720d2fb5ad67e08d11b926b255086579a3bd4b39/third_party/WebKit/Source/core/frame/UseCounter.cpp [modify] https://crrev.com/720d2fb5ad67e08d11b926b255086579a3bd4b39/third_party/WebKit/Source/core/frame/UseCounter.h
,
Aug 11 2016
Closing this as fixed on the Chrome side. If you want to track when it becomes available in the HTTP Archive you can follow the github issue here: https://github.com/HTTPArchive/httparchive/issues/59 |
||
►
Sign in to add a comment |
||
Comment 1 by pmeenan@chromium.org
, Aug 2 2016