BugSplat's new auto-grouping feature is a powerful way to automatically group crashes in a way that's meaningful to your team. Normally, crashes are grouped by the top of the call stack. But sometimes this grouping isn't ideal. For example, if the top of your call stack is KERNELBASE!RaiseException (a Windows OS function) you'd probably prefer the crashes were grouped by a different stack frame. That's what BugSplat's auto-grouping feature does!

Auto-Group Rules

We've got a set of customizable rules that skip over functions that are typically not interesting to application developers. Our default rules are designed to get you started quickly and can be modified as required for each crash report database.

The auto-group rules are pattern-based matching rules that skip irrelevant stack frames and create more meaningful crash groups. Rules can be specified to match either the function or file portion of the call stack.

You can view and change Auto-Group rules on the Settings/Grouping page.

What does this mean for you?

For the majority of BugSplat users, the new auto-grouping rules will not require any action on their part. The rules are intended to improve the accuracy of crash groups without requiring additional input from the user. Typically one team member will review/modify the rules and adapt them for your team's use. If you are that team member, read more about this feature at https://docs.bugsplat.com/introduction/development/grouping-crashes#auto-group-rules

If you have any issues or concerns, please contact us at support@bugsplat.com. We're always here to help you get the most out of BugSplat and ensure that your application is running as smoothly as possible.