once we've got symbols stored in s3 and any incoming symbols syncing to s3 we'll need to get the processors relying on s3 as the source of symbols. This will likely mean implementing a symbol cache so that we aren't hitting the network all the time.
Once bug 1118446 lands we'll just need to change the processor configuration to pass the following commandline options to the stackwalker: --symbols-url : This should be the base URL of the S3 bucket we're using, like https://s3.amazonaws.com/symbols/. --symbols-cache : This should be a local directory in which the stackwalker can cache downloaded symbols. We'll likely need to finish up the work in bug 981079 so we can keep the symbol cache disk usage bounded.
Assignee: nobody → rhelmer
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.