Closed
Bug 853452
Opened 12 years ago
Closed 11 years ago
Add devices to a Signature Summary matview
Categories
(Socorro :: Webapp, task)
Socorro
Webapp
Tracking
(Not tracked)
RESOLVED
FIXED
57
People
(Reporter: kairo, Assigned: brandon)
References
Details
(Whiteboard: [qa-] [DB Changes])
At least for those products that report devices (right now, FennecAndroid, B2G, WebappRuntimMobile), we should add a list of affected devices to the Signature Summary.
We already added reporting on devices to report/list in bug 777372, so that explains where to get this information from, bug 847939 might make it easier to get to that data now, but I guess some aggregation work needs to be done here as well.
Assignee | ||
Updated•11 years ago
|
Assignee: nobody → bsavage
Comment 1•11 years ago
|
||
For Signature X - which devices and what percentage per device
See: https://github.com/mozilla/socorro/pull/748/files for target data
For FennecAndroid, B2G, WebappRuntimMobile:
Table should have:
'Signature',
'Android_CPU_ABI',
'Android_Manufacturer',
'Android_Model',
'Android_Version',
count
Comment 2•11 years ago
|
||
For reference for the week of 8/5/2013, we had about 9300 unique devices.
Comment 3•11 years ago
|
||
Commits pushed to master at https://github.com/mozilla/socorro
https://github.com/mozilla/socorro/commit/f8dd6ed2c96d8cf576c608f3131b920e81eb5794
Fixes bug 853452 Adds signature summary for Android Devices
* Added a signature_summary_devices to signature_summary update function
* Adding crontabber support for android_device table
* Added migration to add new tables
https://github.com/mozilla/socorro/commit/16a97bc79c1fb1df34aebaa73180ddb7c6283346
Merge pull request #1441 from selenamarie/bug853452-devices-sigsum
Fixes bug 853452 Adds signature summary for Android Devices
Updated•11 years ago
|
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Comment 4•11 years ago
|
||
Adding needsinfo? - is the ui in place to expose this data or am I simply overlooking it? I'm looking in the #summary section, is this the correct?
Example:
https://crash-stats.allizom.org/report/list?product=FennecAndroid&range_value=7&range_unit=days&date=2013-08-26&signature=JSScript%3A%3AfullyInitFromEmitter%28js%3A%3AExclusiveContext*%2C+JS%3A%3AHandle%3CJSScript*%3E%2C+js%3A%3Afrontend%3A%3ABytecodeEmitter*%29&version=FennecAndroid%3A26.0a1
https://crash-stats.allizom.org/report/list?product=B2G&range_value=7&range_unit=days&date=2013-08-26&signature=mozalloc_abort%28char+const*%29+|+abort+|+js%3A%3Aion%3A%3AIonCode%3A%3Atrace%28JSTracer*%29&version=B2G%3A25.0a1
Flags: needinfo?(sdeckelmann)
Comment 5•11 years ago
|
||
No UI yet! Sorry -- Brandon is working on the UI separately.
Flags: needinfo?(sdeckelmann)
Summary: Add devices to Signature Summary → Add devices to a Signature Summary matview
Comment 6•11 years ago
|
||
(In reply to Selena Deckelmann :selenamarie :selena from comment #5)
> No UI yet! Sorry -- Brandon is working on the UI separately.
Excellent! I eagerly await our army of dataz. Bumping to [qa-]
Whiteboard: [qa-]
Assignee | ||
Comment 7•11 years ago
|
||
I should have filed a separate bug for selena; my bad. Reopening until the UI is complete and dropping the qa- flag, since we will need QA on the new UI.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Whiteboard: [qa-]
Comment 8•11 years ago
|
||
We need to open a separate bug because this change needs to ship before the UI ships.
Status: REOPENED → RESOLVED
Closed: 11 years ago → 11 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Whiteboard: [qa-] [DB Changes]
Updated•11 years ago
|
Target Milestone: --- → 57
You need to log in
before you can comment on or make changes to this bug.
Description
•