Open Bug 970732 Opened 10 years ago Updated 1 year ago

Add crash-reports style reporting for complete call failures (zero packets)


(Core :: WebRTC: Networking, defect, P3)






(Reporter: bwc, Unassigned)



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).
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.
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
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
investigation estimate needed for collaboration with desktop and work for Fx33
Priority: -- → P2
Target Milestone: --- → mozilla33
Target Milestone: mozilla33 → mozilla35
backlog: --- → webRTC+
Rank: 25
Mass change P2->P3 to align with new Mozilla triage process.
Priority: P2 → P3
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
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.