Closed
Bug 1661646
Opened 4 years ago
Closed 4 years ago
Add extra keys to YSOD Telemetry
Categories
(Core :: XML, task)
Core
XML
Tracking
()
RESOLVED
FIXED
82 Branch
People
(Reporter: zbraniecki, Assigned: zbraniecki)
References
(Blocks 1 open bug)
Details
Attachments
(2 files)
47 bytes,
text/x-phabricator-request
|
RyanVM
:
approval-mozilla-beta+
|
Details | Review |
2.53 KB,
text/plain
|
tdsmith
:
data-review+
|
Details |
In bug 1657242 we added basic YSOD telemetry and the numbers are high enough that we want to understand more of what errors are we seeing.
I'm going to add two extra keys:
- error_code based on https://searchfox.org/mozilla-central/rev/ce21a13035623c1d349980057d09000e70669802/parser/expat/lib/expat.h#55
- location as
line:col
Assignee | ||
Updated•4 years ago
|
Assignee | ||
Comment 1•4 years ago
|
||
Assignee | ||
Comment 2•4 years ago
|
||
Attachment #9172591 -
Flags: data-review?(tdsmith)
Comment 3•4 years ago
|
||
Comment on attachment 9172591 [details]
data-review-ysod.txt
- Is there or will there be documentation that describes the schema for the ultimate data set in a public, complete, and accurate way?
Yes, in the probe definition files and the Probe Dictionary.
- Is there a control mechanism that allows the user to turn the data collection on and off?
Yes, the Firefox telemetry opt-out.
- If the request is for permanent data collection, is there someone who will monitor the data over time?
Yes, zbraniecki.
- Using the category system of data types on the Mozilla wiki, what collection type of data do the requested measurements fall under?
Cat 1, technical data.
- Is the data collection request for default-on or default-off?
Default-on.
- Does the instrumentation include the addition of any new identifiers (whether anonymous or otherwise; e.g., username, random IDs, etc. See the appendix for more details)?
No.
- Is the data collection covered by the existing Firefox privacy notice?
Yes.
- Does there need to be a check-in in the future to determine whether to renew the data?
No.
- Does the data collection use a third-party collection tool?
No.
Attachment #9172591 -
Flags: data-review?(tdsmith) → data-review+
Pushed by zbraniecki@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/9fce6294438c Extend YSOD Telemetry with error_code and location. r=froydnj
Comment 5•4 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
status-firefox82:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 82 Branch
Assignee | ||
Comment 6•4 years ago
|
||
Comment on attachment 9172590 [details]
Bug 1661646 - Extend YSOD Telemetry with error_code and location. r?peterv
Beta/Release Uplift Approval Request
- User impact if declined: We'll take another 3 weeks to learn about the error codes YSOD events happen for.
- Is this code covered by automated tests?: Yes
- Has the fix been verified in Nightly?: Yes
- Needs manual test from QE?: No
- If yes, steps to reproduce:
- List of other uplifts needed: None
- Risk to taking this patch: Low
- Why is the change risky/not risky? (and alternatives if risky): This just adds two keys to an YSOD Telemetry event for chrome urls.
- String changes made/needed: None
Attachment #9172590 -
Flags: approval-mozilla-beta?
Comment 7•4 years ago
|
||
Comment on attachment 9172590 [details]
Bug 1661646 - Extend YSOD Telemetry with error_code and location. r?peterv
Approved for 81.0b5.
Attachment #9172590 -
Flags: approval-mozilla-beta? → approval-mozilla-beta+
Comment 8•4 years ago
|
||
bugherder uplift |
status-firefox81:
--- → fixed
Flags: in-testsuite+
You need to log in
before you can comment on or make changes to this bug.
Description
•