Closed
Bug 1479510
Opened 8 years ago
Closed 8 years ago
Add a telemetry probe for the SDP comparer that records failed rust parsings.
Categories
(Core :: WebRTC: Signaling, enhancement)
Core
WebRTC: Signaling
Tracking
()
RESOLVED
FIXED
mozilla63
| Tracking | Status | |
|---|---|---|
| firefox63 | --- | fixed |
People
(Reporter: johannes.willbold, Assigned: johannes.willbold)
Details
Attachments
(1 file)
There needs to be a telemetry probe that records if the rsdparsa fails to parse the SDP.
| Comment hidden (mozreview-request) |
| Comment hidden (mozreview-request) |
Comment 3•8 years ago
|
||
| mozreview-review | ||
Comment on attachment 8996025 [details]
Bug 1479510: Added a telemetry probe that records failed rsdparsa parsings,
https://reviewboard.mozilla.org/r/260296/#review267576
lgtm, it would be nice to know what the rsdparsa errors were if there were no sipcc errors, but I'm guessing that would not be possible from a privacy point of view.
Attachment #8996025 -
Flags: review?(dminor) → review+
| Assignee | ||
Comment 4•8 years ago
|
||
| mozreview-review-reply | ||
Comment on attachment 8996025 [details]
Bug 1479510: Added a telemetry probe that records failed rsdparsa parsings,
https://reviewboard.mozilla.org/r/260296/#review267576
Yes, this would basically defeat the approach of catgorizing the errors. We can still add more telemtry if this is a frequent errror.
Pushed by drno@ohlmeier.org:
https://hg.mozilla.org/integration/autoland/rev/dc3cf7417929
Added a telemetry probe that records failed rsdparsa parsings, r=dminor
Comment 6•8 years ago
|
||
| bugherder | ||
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
status-firefox63:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla63
Updated•8 years ago
|
Assignee: nobody → johannes.willbold
You need to log in
before you can comment on or make changes to this bug.
Description
•