Open
Bug 970732
Opened 11 years ago
Updated 2 years ago
Add crash-reports style reporting for complete call failures (zero packets)
Categories
(Core :: WebRTC: Networking, defect, P3)
Core
WebRTC: Networking
Tracking
()
NEW
mozilla35
backlog | webrtc/webaudio+ |
People
(Reporter: bwc, Unassigned)
References
Details
Pretty self-explanatory, although the details of what we actually report need to be defined. It probably should include all of the stuff that about:webrtc covers (ICE stats and logging).
Comment 1•11 years ago
|
||
Note: this needs to ping the user since some level of personally-identifiable info will be exposed to Mozilla. Also the data will need to be protected at our servers, so there's a server side to this. If at all possible, we should leverage existing infrastructure for crash stats.
Privacy review will be required.
Comment 2•11 years ago
|
||
Nils, As we discussed in triage yesterday, this work goes beyond the webrtc team. Doing a needinfo to remind you to talk with Ted about what the design plan for this bug should be (since Ted has done work like this before).
Flags: needinfo?(drno)
QA Contact: drno
Comment 3•11 years ago
|
||
Removing from media quality/connectivity tracking bug
Given the UI, privacy, server and other issues surrounding this, it's better to spend our time making it easier to gather information about a problem. We have other telemetry around call completion, etc.
No longer blocks: 970426
Comment 4•11 years ago
|
||
investigation estimate needed for collaboration with desktop and work for Fx33
Updated•11 years ago
|
Priority: -- → P2
Target Milestone: --- → mozilla33
Updated•11 years ago
|
Target Milestone: mozilla33 → mozilla35
Updated•10 years ago
|
backlog: --- → webRTC+
Rank: 25
Comment 5•7 years ago
|
||
Mass change P2->P3 to align with new Mozilla triage process.
Priority: P2 → P3
Comment 6•7 years ago
|
||
Clearing some old NI... maybe with the dev-tools add-on we are working on we are getting closer to accomplishing this.
Flags: needinfo?(drno)
QA Contact: drno
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•