Closed
Bug 412477
Opened 17 years ago
Closed 16 years ago
add REST api with JSON output
Categories
(Socorro :: General, task, P3)
Socorro
General
Tracking
(Not tracked)
RESOLVED
FIXED
0.8
People
(Reporter: ted, Unassigned)
References
(Blocks 1 open bug)
Details
A REST api with JSON output would be awesome. It would be really cool to be able to get data about a submitted crash report (among other things) in JSON. We could use this in bug 411490 to show the status of a crash and the signature in the browser.
Comment 1•17 years ago
|
||
In-product stuff needs use to scale and cluster this thing a lot better.
Target Milestone: --- → 0.9
Comment 2•17 years ago
|
||
I think that at least initially this would be more useful to allow an extension to extend about:crashes to display useful info. I'm not sure whether that sort of extra info would need to make it to the default product but it could be very helpful for developers and nightly testers.
Updated•16 years ago
|
Target Milestone: 0.9 → ---
Updated•16 years ago
|
Priority: -- → P3
Target Milestone: --- → 0.8
Comment 3•16 years ago
|
||
in Bug 484032, we're moving the dump table data into file system storage. At the same time we're wrapping the dump into a json format and including all the metadata that is stored in the reports table. Our current proposal, however, leaves the dump data itself as just a big block of text rather than breaking it up into json-ified fields. Would that json format work for this idea?
Reporter | ||
Comment 4•16 years ago
|
||
Sounds fine, yeah.
Comment 5•16 years ago
|
||
Per Bug 484032 you can request
http://crash-stats.mozilla.com/dumps/<UUID>.jsonz
if this is a 404, then you need to request
http://crash-stats.mozilla.com/report/index/<UUID>
this will queue up processing the report as a priority job...
We can add more JSON support. Please file a new bug with details.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•13 years ago
|
Component: Socorro → General
Product: Webtools → Socorro
You need to log in
before you can comment on or make changes to this bug.
Description
•