Open
Bug 1295602
Opened 8 years ago
Updated 2 years ago
aboutdebugging: better (UI) telemetry support
Categories
(DevTools :: about:debugging, defect, P2)
DevTools
about:debugging
Tracking
(firefox51 affected)
NEW
Tracking | Status | |
---|---|---|
firefox51 | --- | affected |
People
(Reporter: jdescottes, Unassigned)
References
(Blocks 1 open bug)
Details
about:debugging can be used by several different groups of users: - addon developers - service worker developers As we will keep adding features to about:debugging we need to have a way to track which features in the tool are used. So we need telemetry data for each specific about:debugging category. UI Telemetry is a possible candidate to use here.
Reporter | ||
Comment 1•8 years ago
|
||
Bryan: Jan mentioned you thought about using UI Telemetry for about:debugging. Any advice/pointers we should follow here?
Flags: needinfo?(clarkbw)
Comment 2•8 years ago
|
||
All depends on the questions you want answered. UI Telemetry can help you instrument specific buttons or actions to better understand how people are using the product. If you want to know which tab people are in I believe regular Telemetry could be more useful in reporting that information. A simple keyed count for about debugging that increments with every open of the worker vs. addon tab would allow us to know in aggregate which page is getting used more. Questions I think we want to answer: * What is being used more? The Worker or Add-on tab? - a telemetry probe can answer this, make it opt-out * In the Worker Tab which actions are people using the most? Perhaps you want to know how to make certain actions easier. - this would be a use for UI Telemetry
Flags: needinfo?(clarkbw)
Reporter | ||
Updated•8 years ago
|
Priority: -- → P2
Blocks: dt-telemetry
Updated•6 years ago
|
Product: Firefox → DevTools
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•