Closed Bug 770078 Opened 10 years ago Closed 10 years ago
Display new metadata "Flash
Process Dump" in webapp
Bug 769048 is adding a new piece of metadata to crash dumps on a very tight schedule for Flash 11.3 crash diagnosis. This metadata will be: FlashProcessDump=Broker FlashProcessDump=Sandbox This metadata will only be present on certain "ProcessType=plugin" crashes. As I understand it, this data will automatically be collected and stored in hbase, so all we need to do immediately is change the webapp to display this information publicly when available. In the future I may ask for this data to be stored in the database or even modify the signature generation algorithm, but I don't actually know what I need or want in that regard yet.
If this is in the raw JSON (do you have some test report submitted where we can see that data?) then AFAIK there are easy mechanics in place to just display it in the UI from there.
I believe it should be in the raw JSON, and I'm still working on a submission that makes any sense.
https://crash-stats.mozilla.com/report/index/bp-aef2e9de-e6d8-4283-967a-98f832120702 has a sample report.
And this is in the raw JSON there: "FlashProcessDump": "Sandbox", So, yes, I hope that is easy to add in the UI as AFAIK we have some experience now with exposing stuff from the raw JSON directly in the UI. Laura knows more there, of course. :)
Pull request https://github.com/mozilla/socorro/pull/679 r?
Target Milestone: --- → 15
Commits pushed to master at https://github.com/mozilla/socorro https://github.com/mozilla/socorro/commit/a6159c603c332ef27b4c7f95e88624930bdecbc7 Fixes bug #770078, I hope https://github.com/mozilla/socorro/commit/e1c21655c3e8001acffc49a0011a1a7e528cc272 Merge pull request #679 from lauraxt/770078 Fixes bug #770078, I hope
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
QA verified - I see no regressions although the test signature from comment 3 doesn't exist on stage. https://crash-stats.allizom.org/report/index/bp-aef2e9de-e6d8-4283-967a-98f832120702
You need to log in before you can comment on or make changes to this bug.