Open Bug 1469094 Opened 6 years ago Updated 2 years ago

Add telemetry to record possible causes of discovery/connection failure (USB)

Categories

(DevTools :: about:debugging, enhancement, P3)

Product:
DevTools
Component:
about:debugging
Type:
enhancement

Tracking

(Not tracked)

People

(Reporter: birtles, Unassigned)

References

(Blocks 2 open bugs)

Details

(Whiteboard: old-remote-debugging-ng-m3) 

Once we can connect to USB devices and wi-fi devices from about:debugging, we should log information necessary to identify failed attempts at discovery/connection that will help us reduce the failure rate in future.
Priority: -- → P3
Moving major about:debugging ng work into milestone 1, leaving m0 for prior bugfix work.
Blocks: remote-debugging-ng-m1
Focused on USB, will block m2 or m3.
Summary: Add telemetry to record possible causes of discovery/connection failure → Add telemetry to record possible causes of discovery/connection failure (USB)
Priority: P3 → P2
No longer depends on: 1469089
We have moved our telemetry work to m3 .
Blocks: remote-debugging-ng-m3
No longer blocks: remote-debugging-ng-m2
Priority: P2 → --
filter on remote-debugging-next-move-m3-to-m2
Blocks: remote-debugging-ng-m2
filter on remote-debugging-next-move-m3-to-m2
filter on remote-debugging-next-move-m3-to-m2
No longer blocks: remote-debugging-ng-m3
Priority: -- → P2
Whiteboard: old-remote-debugging-ng-m3
Priority: P2 → P3

Add a more detailed overview of the events to implement after Bug 1521507 has been resolved.

Depends on: 1521507
Flags: needinfo?(jdescottes)
Flags: needinfo?(jdescottes)
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.