Rollbar supports multiple messaging tools, where your team can get notified about errors and significant events. Integrating a messaging tool with your Rollbar projects helps you manage the incoming alerts, so you won’t overlook any essential event in your projects while you are not overloaded with messages. This way, you can focus on the important things: fixing bugs.
In this article, we will focus on the most popular notification integration: Slack. We will cover:
- the benefits of using Slack integration in your projects,
- the perks of using Slack Actions, and
- tips and tricks to get the most out of using Slack (or other) notifications.
So let’s get to it then!
Slack is one of the most commonly used options for notification integration for Rollbar projects. Once Slack is integrated with Rollbar, default rules will have been created for your projects, ready to be used. You can also customize these rules and set them up to make sure they serve your team the best (and least annoying) way.
With the help of notifications, you can:
- set-up the types of notifications you are interested in,
- add notification filters, to keep the messages relevant and limit the number of alerts,
- include notification variable values to customize the content of the messages based on the type of event that triggers the notification.
With these set-ups, you can make sure that notifications are only triggered in specific conditions, with tailored messaging that fits your needs. For example, you can set-up an alert for new items happening in the production environment, with severity level ‘Error’ or higher. Neat right?
Moreover, you can act on these notifications without having to leave Slack.
All about Slack Actions
Slack Actions makes managing your items more comfortable without leaving Slack. When Slack notifies you about an event, you will have the action options available right under the notifications, so you can quickly and conveniently act upon them. With the help of Slack Actions, you will be able to:
- edit the status of an item, e.g., you can quickly resolve, mute, or reopen items,
- change the severity level of an item,
- assign items to teammates.
When a new alert pops-up in Slack, you can easily assign it to your relevant teammate, mark its severity level, and set the status depending on how you want to handle it.
Actions can be enabled or disabled for all notifications within your projects and the individual notification rules.
Reduce noise with these tips & tricks
Here are 5+1 quick tips to take your notifications to the next level!
- Make sure to configure which messages go to which channel, as some might only be relevant to a specific group of users. You can set-it up on the individual rules, making sure that each notification only pops up at the appropriate channel.
- In case you want to mention specific users in the Slack message, you can use the <@username> syntax.
- To make sure that the right group or team receives the relevant notifications, you can use Slacks default @here @channel @group @everyone mentions as well, you simply have to use the appropriate syntaxes: <!here> <!channel> <!group> <!everyone>.
- Use any data value sent in the JSON payload of an item or occurrence as a variable, including custom data to customize your message. (additional explanation??)
- Notifications API is available at Rollbar! You can update notification settings and rules programmatically for all of your projects all at once. You can also check our blog post on Notifications API for more details.
+1. Not a fan of API? You can easily replicate notification settings and rules from one project to another with just the click of a button at the bottom of the Notification Settings page of the project. Just select the project with the preferred notification settings and hit Replace!