the new correlation reports need to have things like addon-name, addon-url, etc. We don't have that in Postgres. We need a method to get the data from AMO and then continually maintain it on at least a daily basis.
What does the current script do there? Where do we have the source of the script that does the current reports (I'd like a look at the script for other purposes as well)?
(In reply to Robert Kaiser (:firstname.lastname@example.org) from comment #1) > What does the current script do there? > Where do we have the source of the script that does the current reports (I'd > like a look at the script for other purposes as well)? The existing correlation scripts are http://hg.mozilla.org/users/dbaron_mozilla.com/crash-data-tools/ and the cronjob which runs it looks like https://github.com/mozilla/socorro/blob/master/scripts/crons/cron_libraries.sh Pretty sure the AMO name/url/id information is checked in here: http://hg.mozilla.org/users/dbaron_mozilla.com/crash-data-tools/file/7cdfea7cdb3b/addonids-amo.json
FYI, it looks like we're already accessing the AMO API somewhere, see bug 722462
(In reply to Robert Kaiser (:email@example.com) from comment #3) > FYI, it looks like we're already accessing the AMO API somewhere, see bug > 722462 That's called by the PHP app to populate the "Extensions" tab on the reports page for example: https://crash-stats.mozilla.com/report/index/0f3f3360-40a6-4188-8659-b2a5c2110808 Having a cron job populating a table in postgres (as we do for bugs from bugzilla and releases from FTP) would probably good a good replacement for both this and correlation reports.
old and outdated - refile if this is still needed
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.