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 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.
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 your error occurrences. Learn more about Grouping.
The Rollbar grouping algorithm is smart and is constantly improving, 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 bug fixing 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 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 we would rather create additional unique items for occurrences that cannot be clearly grouped into existing items than risk a bug going 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,
You can manually merge items together, thus combining items into one new group for easier management. In this case, all past and future occurrences of those items will be combined automatically, and you will have one unified view on the Item details page of all the occurrences of the error.
Manually merging your items comes in handy when the grouping algorithm separates items that you think should rather go together. You can then group them instantly with the merging option. It is also useful when you want to group items that do not require their custom fingerprint.
If you want to remove items from a group because they were mistakenly grouped or you decided to organize the occurrences separately, you have the chance to un-merge them. From then on, they will be handled as separate items.
Create a custom fingerprinting rule, so it applies to all future occurrences that comply with the rule.
When you manually merge items, Rollbar will analyze the items. If it can spot a discernible common pattern, then the system will automatically offer you the option to create a new easily custom fingerprint on the spot. This custom fingerprint will automatically apply to all future occurrences and combine them into the new item group.
Custom fingerprints allows you to set up precise rules combining certain occurrences and generating new fingerprints. This is especially useful if you want to handle certain errors in the same way, together, regardless of their stack trace, and you want to avoid having to merge multiple items manually. You can also easily keep an eye on the custom fingerprints that are created for your projects in the Custom Fingerprinting Version History.
Updated about 1 month ago