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.

When you merge multiple items, Rollbar will now try to suggest a custom fingerprint rule to combine similar exceptions in the future.

The first release of this feature detects items with the same exception class and similar exception messages and automatically generates the JSON fingerprinting rule for detecting future occurrences.

Feedback? Questions? Suggestions?

This is the first of many upcoming improvements that will increase the relevance of your exception data in Rollbar. We're eager to hear from you to learn how well it's working!

Just send us a message via the in-app chat and someone will respond as quickly as possible.

Ruby 2.6.0 introduced a new bug bug (#15472 - Invalid JSON data being sent from Net::HTTP in some cases with Ruby 2.6.0) that may result in the Rollbar API returning an error when an exception is reported. (See rollbar-gem issue #797).

Until the Ruby maintainers have released the fix for this bug, we advise Rollbar users to not upgrade their applications to Ruby 2.6.0.

The search in Items view now supports an exception operator to search by exception class. To view all search operators check out our search docs.

Questions?

Send us a message via the in-app chat or via support@rollbar.com.

When creating a new project you now have the option to choose whether or not email notification rules will be added. .

This is handy if you prefer to use a different notification channel (e.g. Slack).

We've made it easier for your teammates to join your account when you've enabled signup via whitelisted email domains.

To enable signup via a whitelisted email domain, go to Account Settings → General.

Your teammates will have the option to join your account after they've verified their email address.

Questions? Feedback?

Send us a message at support@rollbar.com or via the in-app chat. We're here to help!

Previously, new notification rules were created without any filters applied, often leading to noisy notifications (e.g. emails for every occurrence).

You can now edit a notification rule before it's created: