Webinar: Continuous Code Improvement Series | How to Improve with AI-Assisted Workflows Register Here Today!
September 22nd, 2020 • By Gabriella Papp
Congratulations on setting up your Rollbar projects! You took a step towards more visibility and an easier flow when it comes to debugging. Now, you might as well learn how the incoming errors are examined and grouped together by Rollbar. Let’s see how it happens and what else do we have to offer!
With the help of Rollbar’s default grouping algorithm, you will: ● Keep your items list transparent and organized, ● Reduce the noise in your notifications, ● Understand and respond to your errors better.
Learn how Rollbar groups your items by default
Error grouping means that when you release a code to production, and it crashes hundreds of times, our system groups all of those crashes together in one error item and sends you one notification, instead of notifying you every time, resulting in 100 notifications in your inbox. The 1 item in your items list will include all the details of all the occurrences of your error.
The Rollbar grouping algorithm is smart and is being improved constantly, so we can serve our customers. Rollbar tries to group occurrences together with the same root cause in one item so that you: ● Have visibility over all the occurrences of one error item, which makes you ● Understand your errors a lot easier, and ● Speed up the bugfixing process.
The occurrence fingerprints are resilient to deploys and code changes, so you can track the history of your occurrences through multiple deploys and code versions.
Take your Grouping to the next level
It is also important to mention, that our default grouping algorithm is designed to be adequate for most projects. However, you might want to have a more customized experience. Well, this is when you can make good use of merging or custom fingerprinting.
Rollbar errs on the undergrouping. This means that we would rather create additional unique items for occurrences that cannot be clearly grouped into any existing items, than risk a bug go unnoticed by the developers in the noise.
If you think our algorithm skipped grouping errors that you think belong together, you can: ● Merge them manually, and group all past and future occurrences together, ● Create a custom fingerprinting rule, so it applies to all future occurrences that comply with the rule.
Learn more about merging vs. custom fingerprinting
Check out our article on Merging vs. Custom Fingerprints to see the benefits for each and understand how to use them to make your projects more transparent and better organized.