Closed Bug 492017 Opened 16 years ago Closed 16 years ago

provide RSS feed of latest crashes

Categories

(Socorro :: General, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: ted, Assigned: ozten)

References

Details

Attachments

(1 file)

I'd like to have an RSS feed of "latest crashes" or something like that, so I could look at some subset of crashes to get a list of modules for bug 419882. Ideally I'd be able to get a feed of just Windows crashes, but it wouldn't be a big deal to filter them by OS client-side. Also, if the feed could provide a direct link to the JSON that would be pretty helpful.
Blocks: 419882
Attached file Output of atom feed
Attaching the output of going to http://aking.khan.mozilla.org/reporter/feed/reports_by_product/Firefox/3.0b4pre/windows The url for recent crashes by product would be /feed/reports_by_product/{product}/{version} - Across OS /feed/reports_by_product/{product}/{version}/{platform} - OS specific platform - [null|ALL|windows|mac|linux|solaris]
This looks great, thanks! My only caveat would be that I don't actually care about product, I'd be happy to just get reports across all products and versions, filtered down by OS. My ultimate goal here is just to get a good sampling of crashes on Windows and look at the module lists. Actually, come to think of it, having the product version in there might be a pain, since I'm going to have this script on a cron job, and I don't want to have to update the version to the latest whenever we release a security fix. Could you provide at least one of the following: /feed/reports_by_product/{product}/{platform} - reports for {product} on {platform} across all versions /feed/reports/{platform} - reports for all products on {platform} The latter would be my preference. The feed content itself looks useful, although my application isn't going to look at the <summary>, so if you wanted to trim that down it wouldn't matter to me. FeedParser handles it just fine and I can grab the link to the JSON quite easily.
(In reply to comment #1) > Attaching the output of going to > http://aking.khan.mozilla.org/reporter/feed/reports_by_product/Firefox/3.0b4pre/windows I just noticed that the link URLs in here all point to crash-stats.mozilla.com. Presumably that will be fine for production, but it makes it a bit hard to test this staging copy.
Assignee: nobody → ozten.bugs
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Component: Socorro → General
Product: Webtools → Socorro
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: