Confirmed users, Bureaucrats and Sysops emeriti
1,531
edits
Breakpad/Design: Difference between revisions
→Airbag Database
ChrisHofmann (talk | contribs) |
ChrisHofmann (talk | contribs) |
||
| Line 59: | Line 59: | ||
** [need to dig up all common queries - jay] | ** [need to dig up all common queries - jay] | ||
* The schema now accounts for the following kinds of information | * The schema now accounts for the following kinds of information | ||
** individual blackbox records | |||
** product/OS information to match up stack info with the right location in symbol store to find symbols | |||
** control information use to "register" an incoming blackbox and monitor/track/control its progress though all the stages from being transfered from the client until it is fully collected and digested on the server and available for reporting and analysis. | |||
* using the same database and schema for the blackbox data and also for control over the processing of the blackboxes has created problems in the past. when coruption is introduced, database performance problems crop up, or maintenance is required to manage the collection of blackboxes, the processing of incoming blackboxes is hindered and we start into a downward spiral of compounding problems. We should do some thinking to see if there are ways to improve on the existing design. | |||
== Analysis and Reporting System(s) == | == Analysis and Reporting System(s) == | ||