Open
Bug 1402459
Opened 8 years ago
Updated 11 months ago
Track usage of console's filtering features
Categories
(DevTools :: Console, enhancement, P3)
DevTools
Console
Tracking
(firefox57 fix-optional, firefox58 affected)
NEW
| Tracking | Status | |
|---|---|---|
| firefox57 | --- | fix-optional |
| firefox58 | --- | affected |
People
(Reporter: jryans, Unassigned)
References
(Blocks 2 open bugs)
Details
In the console, there are filtering features that are off by default. It would be good to know how much they are used, to better plan time spent recording the messages that they reveal.
In particular, I am curious about:
* How many console sessions have the filter bar (devtools.webconsole.ui.filterbar, off by default) enabled?
* How many console sessions have CSS messages (devtools.webconsole.filter.css, off by default) enabled?
* How many console sessions have XHR messages (devtools.webconsole.filter.netxhr, off by default) enabled?
* How many console sessions have Requests messages (devtools.webconsole.filter.net, off by default) enabled?
| Reporter | ||
Comment 1•8 years ago
|
||
(I guess the session counts should be tracked in a similar way to console opens, so that we can derive usage percentages by using total console sessions as the denominator.)
Comment 2•8 years ago
|
||
Good idea - this would help us make decisions about the new ui
status-firefox57:
--- → fix-optional
Priority: -- → P2
Comment 3•8 years ago
|
||
Docs for adding telemetry are here: https://dxr.mozilla.org/mozilla-central/source/devtools/docs/frontend/telemetry.md
Updated•8 years ago
|
Blocks: console-filtering
Updated•7 years ago
|
Product: Firefox → DevTools
Comment 4•7 years ago
|
||
Bug 1463095 added telemetry for filter changes. This is not exactly what this bug was about but seems close.
See Also: → 1463095
Updated•3 years ago
|
Severity: normal → S3
Updated•11 months ago
|
Blocks: dt-telemetry
Priority: P2 → P3
You need to log in
before you can comment on or make changes to this bug.
Description
•