In case you’re using client-side fingerprinting, you may want to consider turning it off in favor of server-side fingerprinting.

You now have the option to do so by going to Settings>Setup>Custom Fingerprinting.

By using client-side fingerprinting, you won't enjoy the benefits of improvements to our grouping algorithm. Therefore, we highly recommend you activate this option and let us know if you have any grouping-related issues in the future.

Questions? Feedback?

Let us know what you think by sending an email to support@rollbar.com or a message via the in-app chat.

You now have the option to group together all occurrences where the only difference is the number of recursive calls.

To activate this you can go to Settings>Advanced>Migrations, tick the relevant checkbox, and push Save changes.

We suggest enabling this option for every project. However, note that you might receive a number of 'New Item' notifications initially since this change is not retrospective.

Please be aware that this option is enabled by default for new projects and won't be visible.

Questions? Feedback?

Let us know what you think by sending an email to support@rollbar.com or a message via the in-app chat.

By default, we include the code context (source code fragment) of Python stack frames in the string used for fingerprinting. Including the code context means that any time a change is detected, however small it might be, a new item will be created. As a result, even if you only change code formatting or rename a variable, you will get a 'New Item' notification.

You can now disable this for any project by going to Settings>Setup>Custom Fingerprinting.

However, note that disabling it may result in overgrouping when the method names are not unique, like in the case of inner functions and lambdas.

Also, this change is not retrospective, so expect an initial flurry of 'New Items'.

Questions? Feedback?

Let us know what you think by sending an email to support@rollbar.com or a message via the in-app chat.

Occurrences related to missing jQuery have been creating multiple items so far. By enabling our improvement, you can group all such future occurrences together into one item, so you can focus on the real errors.

You can activate this improvement by heading over to Settings > Advanced > Migrations and enabling the relevant checkbox.

We recommend enabling this migration for each JavaScript project to ensure you’re using the latest grouping algorithm. Just hit save and Rollbar will immediately start grouping new missing jQuery occurrences into an umbrella item.

Please note that previously created items won't disappear since this change is not retrospective. Give it some time or resolve them once and they will disappear as they won't have any new occurrences.

Additionally, this option is enabled by default for all new projects and won't be visible.

Questions? Feedback?

Let us know what you think by sending an email to support@rollbar.com or a message via the in-app chat.

In order to make reporting grouping issues easier we've made the Report overgrouping button available on Occurrence pages as well, not just on Item pages.

If you want to let us know that a specific occurrence is in the wrong item, you can now click on the Report overgrouping button on the Occurrence page. If you just want us to know that an item contains occurrences that do not belong to the item, you can click on the button on the Item page.

Questions? Feedback?

We're eager to hear what you think! Just send an email to support@rollbar.com or a message via the in-app chat.

Since we added a Report overgrouping button a few weeks ago to give you the ability to report grouping issues, we received some accidental clicks. We've updated the button with a confirmation box to prevent unintentional overgrouping reports.

Questions? Feedback?

We're eager to hear what you think! Just send an email to support@rollbar.com or a message via the in-app chat.

Triaging exceptions in Rollbar just got much easier!

With the new action menus in Slack, you can

• Assign items to teammates.
• Resolve, mute, or reopen items.
• Change the level to severe, warning, etc.

Prefer to keep your Slack notifications read-only? The action buttons can be enabled/disabled on a per-notification rule basis so you have full control!

To enable Slack action buttons you may need to refresh your authorization token. Just click the link in the in-app banner and ensure that an updated token is used for your Slack notification rules.

Questions? Feedback?

We're eager to hear what you think! Just send us an email via support@rollbar.com or a message via the in-app chat.

If some occurrences shouldn't have been grouped in an item you can now report it via the Report overgrouping button. It can be found at the top of group item pages, directly next to Mute.

We will use your feedback to improve our grouping algorithm. For more information on how we group by default, check out the Docs.

Additional Feedback or Questions?

We're working on a number of grouping improvements and every feedback helps. Let us know what you think by sending an email to support@rollbar.com or by messaging us via the in-app chat.

Since we introduced fingerprint rule suggestions a couple of weeks ago, several users have asked to be able to edit the rules before creating them. We've just launched this improvement, complete with JSON syntax highlighting.

Check out our custom fingerprint rule docs for a complete guide to defining your own rules.

If your organization has a lot of projects, you may be receiving email notifications for projects that are maintained by other teams. It's now possible to turn on/off email notifications per project via your personal email settings.

To update your settings, go to User Settings → Email Settings.