17
edits
Breakpad:Feature List: Difference between revisions
m
Airbag renamed to Breakpad; references adjusted
(→General: link to my list of webtool issues) |
m (Airbag renamed to Breakpad; references adjusted) |
||
| Line 1: | Line 1: | ||
'''[[ | '''[[Breakpad|« back to Breakpad main page]]''' | ||
This page is for listing ideas about what | This page is for listing ideas about what Breakpad's web interface could do for us. | ||
= Talkback Features to Reimplement = | = Talkback Features to Reimplement = | ||
| Line 11: | Line 11: | ||
** Depending on what type of data we end up collecting from clients, we need to make sure we create a similar query tool to what exists now at http://talkback-public.mozilla.org | ** Depending on what type of data we end up collecting from clients, we need to make sure we create a similar query tool to what exists now at http://talkback-public.mozilla.org | ||
* Talkback Reports | * Talkback Reports | ||
** The current reports availabe through http://talkback-public.mozilla.org provide a lot of useful information that is easy to digest from release to release and on the dev. branches. The current set of reports are generated daily from Talkback data dumps of 10 days worth of crashes. The scripts are pretty old and should not be reused. Changes to what we collect from | ** The current reports availabe through http://talkback-public.mozilla.org provide a lot of useful information that is easy to digest from release to release and on the dev. branches. The current set of reports are generated daily from Talkback data dumps of 10 days worth of crashes. The scripts are pretty old and should not be reused. Changes to what we collect from Breakpad will help us decide what types of reports we can create. | ||
** I would like to determine which reports are most useful and then do a rewrite of the scripts or create better web apps to provide better | ** I would like to determine which reports are most useful and then do a rewrite of the scripts or create better web apps to provide better Breakpad data. | ||
* MTBF (Mean Time Between Failure) | * MTBF (Mean Time Between Failure) | ||
** We need to make sure | ** We need to make sure Breakpad is able to collect and report information about session times of clients between crashes, since install, frequency of crashes, etc.. | ||
** MTBF reports for major releases are critical to comparing stability between releases. | ** MTBF reports for major releases are critical to comparing stability between releases. | ||
** We used to have MTBF reports and graphs across releases, but I could not get them working, so we currently rely on the daily MTBF calculations in the Talkback Reports. | ** We used to have MTBF reports and graphs across releases, but I could not get them working, so we currently rely on the daily MTBF calculations in the Talkback Reports. | ||
| Line 22: | Line 22: | ||
= Symbol Collection = | = Symbol Collection = | ||
* In addition to symbol collection from Windows and from tinderboxen (discussed elsewhere), we should have facilities to upload a PDB file to the server. This can be used to provide symbols for plugins and extension DLLs. | * In addition to symbol collection from Windows and from tinderboxen (discussed elsewhere), we should have facilities to upload a PDB file to the server. This can be used to provide symbols for plugins and extension DLLs. | ||
** Considering that plugins and extensions are responsible for the majority of our crashes (don't quote me on it) and most of our "stack signatures" are Windows system .dlls, this should be a high priority feature for our | ** Considering that plugins and extensions are responsible for the majority of our crashes (don't quote me on it) and most of our "stack signatures" are Windows system .dlls, this should be a high priority feature for our Breakpad server. | ||
* Maintenance, cleanup, and backup scripts/tools should be designed into the symbols uploading/storage architecture to save people the headache of monitering symbols storage space. | * Maintenance, cleanup, and backup scripts/tools should be designed into the symbols uploading/storage architecture to save people the headache of monitering symbols storage space. | ||