Power User Series is a series in which we give you the tips, tricks and tutorials to get the most value from Rollbar and help you and your team become power users.
You're two weeks into using Rollbar. You've watched in amazement as issue after issue comes in without a single customer complaint to accompany them. How did you ever find errors before!?
Now that your unresolved errors have drastically decreased, you've started to notice a handful of Rollbar items that all seem to be exactly the same issue. Maybe you've been notified that your UI has exceeded the maximum call stack when calling a particular function. And in one case you found out that your database is actually missing several columns which got grouped into a single error.
What's a new Rollbar user to do? Here's 6 steps to help you improve your error grouping in Rollbar:
1. Learn how Rollbar groups items.
The Rollbar grouping algorithm attempts to be as smart as possible by grouping items by root cause. Error type items are grouped by a combination of platform, environment, error class, and stack trace information. Message type items are grouped by message text after stripping out certain number-like and date-like portions of the message.
2. Customize your error grouping.
Custom grouping enables you to decide exactly how Rollbar will group your items. You can alter the title, change the fingerprinting (and therefore the grouping), and use any data you send to us to make it work!
3. Make sure you're setting the server root.
Before grouping by filename, Rollbar will strip off whatever you're sending in the server root segment. This means that you can host the code from varying locations, but still get the same grouping, no matter where on the system you host your code. Each notifier allows setting this in its own way. Check out the docs for your notifier to learn how!