Open Bug 1402459 Opened 4 years ago Updated 3 years ago

Track usage of console's filtering features

Categories

(DevTools :: Console, enhancement, P2)

enhancement

Tracking

(firefox57 fix-optional, firefox58 affected)

Tracking Status
firefox57 --- fix-optional
firefox58 --- affected

People

(Reporter: jryans, Unassigned)

References

(Blocks 1 open bug)

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?
(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.)
Good idea - this would help us make decisions about the new ui
Priority: -- → P2
Product: Firefox → DevTools
Bug 1463095 added telemetry for filter changes. This is not exactly what this bug was about but seems close.
See Also: → 1463095
You need to log in before you can comment on or make changes to this bug.