The size of your install base doesn’t matter. We work with applications that process several hundred reports per year up to applications that submit hundreds of millions of reports a year.
The magic lies in BugSplat’s ability to sort crash data in a way that makes the data useful to your team no matter the number of crash reports. Are you processing a large number of crash reports? You’ll probably focus on the defects creating the largest number of crashes. Are you concerned about every single crash report created? No problem, as BugSplat will handle that use case too.
A great example of how BugSplat handles crashes is the Dashboard page. This tool provides a view of the stability of your application in an easy-to-use line graph, visually helping you see how your software is performing for users.
To get more detailed information on crashes, use the Summary page to see your crash data organized by their crash signature (or StackKey).
By looking at the Count column, you can see exactly how many times a particular crash defect caused your software to crash. You can then drill into that crash defect to inspect all the individual crash reports that are associated with the StackKey.
Because your crashes are automatically organized, you don’t have to waste time guessing which crash defects need your attention. Whatever Stack Key’s are near the top of your Summary page should absolutely command your team’s attention.