Closed
Bug 1082933
Opened 10 years ago
Closed 10 years ago
about:webRTC exports logs to post on crash stats
Categories
(Hello (Loop) :: General, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1024568
backlog | Fx36+ |
People
(Reporter: shell, Unassigned)
References
Details
When questions go to the forum for support (if answers could not be found in SUMO) then users should be able to send crash reports to Crash Stats. this allows them to upload to crash stats and just put a link in the forum. Only internal folks (at Moz or TokBox can see these to troubleshoot). eliminated needing email addresses to send logs back and forth and aligns with current support flows. Robert Kaiser is your guy for Crash Stats questions. Email: rkaiser@mozilla.com We also have a dev group who created or implemented the API to link to the crash report on our forum. Ricky Rosario would be the guy to talk to for that.
Reporter | ||
Updated•10 years ago
|
backlog: --- → Fx36+
Comment 1•10 years ago
|
||
Shell, please can we start from where this requirement has come from and the user story rather than a technology basis. Whilst crash stats may have some relevant technologies, there's not enough information here as to what we actually want to do, to be able to assess that. For instance about:support may be more relevant/closer, but additionally maybe this is already submitted via the ice reports wrt telemetry. The sort of information we need is: - What is the generally expected user flow? - When/How is the information generated? - What information is actually required by support? -- e.g. Which parts are the most useful, do we need all of about:webrtc, including generated logs whilst in-call? - Who's doing the direct support? - Is the information to be collated, or just reported per-individual? (or both!)
Flags: needinfo?(sescalante)
Comment 2•10 years ago
|
||
Also xref bug 1056922
Reporter | ||
Updated•10 years ago
|
Status: NEW → RESOLVED
Closed: 10 years ago
Flags: needinfo?(sescalante)
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•