Closed
Bug 948123
Opened 11 years ago
Closed 11 years ago
Add CPU information as a column in crash reports table
Categories
(Socorro :: Webapp, task)
Socorro
Webapp
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: away, Unassigned)
References
Details
I'd like to be able to see CPU information (family/model) as an available column on the reports table. (for example the Reports tab at https://crash-stats.mozilla.com/report/list?product=Firefox&signature=nsStyleContext%3A%3ADoGetStyleOutline%28bool%29 )
Comment 1•11 years ago
|
||
From IRC: dmajor: basically I want to see CPU info and BIOS info on the same page, and don't really care which page that is :) :adrian -- would this be something we can do in super search?
Flags: needinfo?(adrian)
To clarify: The reports table currently allows BIOS manufacturer but not CPU info. Super search currently allows CPU info but not BIOS manufacturer. I would like to be able to see both on the same page.
Comment 3•11 years ago
|
||
The BIOS_Manufacturer is in the raw crash and will be made available in super search with bug 944432. Would that be a good solution?
Flags: needinfo?(adrian)
Comment 4•11 years ago
|
||
The set in the Reports tab of report/list is currently limited but is planned to be extended AFAIK, but I don't know any timeline and am not sure who works on that.
(In reply to Adrian Gaudebert [:adrian] from comment #3) > The BIOS_Manufacturer is in the raw crash and will be made available in > super search with bug 944432. Would that be a good solution? Yeah, I think that would work.
Comment 6•11 years ago
|
||
This is working now, you can display both BIOS Manufacturer and CPU info side by side: https://crash-stats.mozilla.com/search/?product=Firefox&version=29.0a1&_facets=bios_manufacturer&_columns=signature&_columns=bios_manufacturer&_columns=cpu_info However, due to a problem in the elasticsearch mapping, the BIOS Manufacturer field is not searchable. Will be fixed by bug 949367.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•