Whitelist IPCFatalErrorProtocol and IPCFatalErrorMsg field to be public in Metadata tab

RESOLVED FIXED

Status

RESOLVED FIXED
2 years ago
2 years ago

People

(Reporter: mccr8, Assigned: adrian)

Tracking

(Blocks: 1 bug)

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

2 years ago
Bug 1191976 added these fields. It would be nice to be able to see them in crash stats because while they mostly correspond to the particular crash stack, the line numbers are in generated code, making it hard to figure out where exactly they were.

Here are some example crash reports:
https://crash-stats.mozilla.com/report/index/4123a507-3fee-4af6-af62-94cfa2160325
https://crash-stats.mozilla.com/report/index/6303d641-c8e3-4610-9d95-03bc02160326
https://crash-stats.mozilla.com/report/index/823ace2c-9be2-4a56-8b43-a341d2160323
(Reporter)

Updated

2 years ago
Blocks: 1259480
(Reporter)

Updated

2 years ago
Blocks: 1259192
Assignee: nobody → adrian
(Assignee)

Comment 1

2 years ago
Done! Both fields are whitelisted and added to SuperSearch as `ipc_fatal_error_msg` and `ipc_fatal_error_protocol`. 

Here's an example in SuperSearch: https://crash-stats.mozilla.com/search/?product=Firefox&ipc_fatal_error_msg=!__null__&_facets=ipc_fatal_error_msg&_facets=ipc_fatal_error_protocol&_columns=ipc_fatal_error_msg&_columns=ipc_fatal_error_protocol

Note that the `ipc_fatal_error_msg` facet will start working next week, since I had to change the mapping of that field. At the moment it shows no data.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → FIXED
Created attachment 8736355 [details]
Screen Shot 2016-03-30 at 12.04.11 PM.png

Andrew, 
Perhaps Adrian's response was confusing. But we try to kill two birds with one stone. The list of fields SuperSearch uses is re-used for the index page where we list all keys and values under the Metadata tab. 

So if something gets whitelisted for search it also becomes a new row on the Metadata page.
(Reporter)

Comment 3

2 years ago
Thanks!
You need to log in before you can comment on or make changes to this bug.