3,035
edits
(Terminology and logic fixes) |
No edit summary |
||
Line 13: | Line 13: | ||
** Defining component specifications | ** Defining component specifications | ||
** Milestones for each component | ** Milestones for each component | ||
== bsmedberg's email, to process later == | |||
Data stores: | |||
A) symbol store - large, fairly static flat-file store | |||
B) minidump store - smaller, constantly changing temporary minidump storage area | |||
C) database | |||
Functions: | |||
1) the collector accepts the crash reports (minidump + metadata) from clients | |||
Requires write access to the minidump store | |||
read/write access to the database | |||
2) the symbol uploader takes symbol information from | |||
2a) the tinderboxes/build systems | |||
2b) uploaded symbol information from extension authors | |||
Requires write access to the symbol store | |||
and read/write access to the database | |||
3) The processor takes the minidump and turns it into a stack | |||
Requires read/delete access to the minidump store | |||
read/write access to the database | |||
this doesn't need to be (probably shouldn't be) a web app, but a | |||
background daemon | |||
4) The query engine provides reporting and querying from the database | |||
Requires read access to the database | |||
5) symbol store maintenance | |||
Need to clean up old symbol information (e.g. nightly builds greater than | |||
a week old, alphas/betas that are no longer relevant, etc. | |||
Requires delete access to the symbol store | |||
Read/write access to the database | |||
== Airbag Client == | == Airbag Client == |
edits