Development Updates

  • March 18, 2022
    Slack Oauth 2.0 system is available for your Rollbar projects

    Slack Oauth 2.0 system is available for your Rollbar projects

    Rollbar is adopting the updated Oauth 2.0 flow created by Slack. Slack has revised their access tokens and now allows the Rollbar Slack bot to have its own credentials. This replaces the use of member’s credentials. 

    What does this mean?

    You don’t have to switch over, but you should consider the benefits of migrating. To complete the migration, you must add the Rollbar Slack bot to any channels that you'd like to post alerts. 

    What are the benefits of Bot Tokens on Slack?

    • Slack integration will use a single bot token, so there will not be any confusion regarding switching user access tokens.
    • You will have the chance to manually enter the appropriate Slack channel via a text input box, which will eliminate the long load times of a drop-down for channel selection when configuring Slack notifications.
    • When team members leave your Slack workspace, their “owned” tokens do not need to be swapped out as they would today.

    How to migrate to Slack Oauth 2.0?

    We recommend you complete the migration process to ensure continued support of notifications. To start the migration process for the new Slack Oauth 2.0 version, you will need to go to your Account Settings and follow the steps in Rollbar.  

    Migrate to Slack Oauth 2.0

      1. Go to Settings, and select Slack, under Notifications. 2. On the Manage Account Slack Settings page, begin the migration process by clicking on the Add to Slack button. 3. On the upper left corner, select the Slack workplace you want to add the bot to. Review the list of updated permissions and click Allow. 4. You will be redirected to the Manage Account Slack Settings page with a list of Slack channels the bot needs to be added to before you can complete the migration. (If you don’t have access to private channels, we recommend you contact your company’s Slack admin to identify the owner of the private Slack channel to gain access and add the bot to the channel.) 5. Go to your Slack workplace, and invite the bot to the channels. (You can easily add the bot, by sending @Rollbar as a message, and then Slack will prompt you to invite the bot to the channel.) 6. Once you’ve invited the bot, you can go back to the Manage Account Slack Settings page, hit the Refresh list button to see the remaining channels the bot needs to be invited to.  Repeat this, until the list of channels disappears and the No channels pending bot invitation message appears. (You can click the Complete Migration button even if there are still channels in the list. In case you complete migrations without adding the bot to all channels there is a risk that the integration stops working.)   7. Now you can click the Complete Migration button, which will allow Rollbar to post notifications using Slack’s new granular scopes. If you navigate back to the Slack integration in your Project Settings, you will now see the configuration below: If you need help with the setup, do not hesitate to contact us at support@rollbar.com.
  • December 20, 2021
    January 2022 Grouping Update

    January 2022 Grouping Update

    This month we are excited to roll out a new January Grouping Update which significantly improves Grouping quality for some of our more relevant SDKs. Mainly PHP, Ruby, Python and Javascript. This update simplifies over 100 Grouping rules within our Grouping rule set by:
    • Reducing overgrouping with new rules placeholders added and an increase of 4.16% in successful new fingerprints
    • Fixing undergrouping by removing generic rules and decrease of 16.36% in the affected fingerprints
    Finally, and the most exciting part, these improvements have been rolled out automatically for all accounts with auto-upgrade enabled, so you can focus on fixing bugs while we take care of the squashing effort!
  • December 15, 2021
    Update regarding Log4j Java vulnerabilities

    Update regarding Log4j Java vulnerabilities

    Rollbar is aware of the Log4j Java vulnerabilities (CVE-2021-44228 and CVE-2021-45046) and we have updated all the potentially impacted infrastructure and we are making updates available for our Java SDK users. We are dedicated to making sure that Rollbar runs quickly and securely within your applications. Learn about how we’ve addressed the Log4J “Log4Shell” zero-day CVE-2021-44228 and CVE-2021-45046
  • December 7, 2021
    December 2021 Grouping Update

    December 2021 Grouping Update

    We are pleased to announce our December 2021 Grouping Update that significantly improves grouping coverage and quality for some of our most common SDKs. Java, PHP, and Python issues now have from 2% to 6% higher coverage rates allowing users to discover more bugs and respond to them more quickly. Grouping quality has been improved as well by reducing overgrouping of errors caused by generic rules overwriting more specific ones. Additionally, this release improves our internal pattern standardization for easier rule management. We can continue training our models more efficiently and analyzing millions of crashes to distinguish different error types accurately. Best of all, these improvements have been rolled out automatically for all accounts with auto-upgrade enabled, so you can focus on squashing and fixing bugs!

Slack Oauth 2.0 system is available for your Rollbar projects

Rollbar is adopting the updated Oauth 2.0 flow created by Slack. Slack has revised their access tokens and now allows the Rollbar Slack bot to have its own credentials. This replaces the use of member’s credentials. 

What does this mean?

You don’t have to switch over, but you should consider the benefits of migrating. To complete the migration, you must add the Rollbar Slack bot to any channels that you'd like to post alerts. 

What are the benefits of Bot Tokens on Slack?

  • Slack integration will use a single bot token, so there will not be any confusion regarding switching user access tokens.
  • You will have the chance to manually enter the appropriate Slack channel via a text input box, which will eliminate the long load times of a drop-down for channel selection when configuring Slack notifications.
  • When team members leave your Slack workspace, their “owned” tokens do not need to be swapped out as they would today.

How to migrate to Slack Oauth 2.0?

We recommend you complete the migration process to ensure continued support of notifications. To start the migration process for the new Slack Oauth 2.0 version, you will need to go to your Account Settings and follow the steps in Rollbar.  

Migrate to Slack Oauth 2.0

  1. Go to Settings, and select Slack, under Notifications. 2. On the Manage Account Slack Settings page, begin the migration process by clicking on the Add to Slack button. 3. On the upper left corner, select the Slack workplace you want to add the bot to. Review the list of updated permissions and click Allow. 4. You will be redirected to the Manage Account Slack Settings page with a list of Slack channels the bot needs to be added to before you can complete the migration. (If you don’t have access to private channels, we recommend you contact your company’s Slack admin to identify the owner of the private Slack channel to gain access and add the bot to the channel.) 5. Go to your Slack workplace, and invite the bot to the channels. (You can easily add the bot, by sending @Rollbar as a message, and then Slack will prompt you to invite the bot to the channel.) 6. Once you’ve invited the bot, you can go back to the Manage Account Slack Settings page, hit the Refresh list button to see the remaining channels the bot needs to be invited to.  Repeat this, until the list of channels disappears and the No channels pending bot invitation message appears. (You can click the Complete Migration button even if there are still channels in the list. In case you complete migrations without adding the bot to all channels there is a risk that the integration stops working.)   7. Now you can click the Complete Migration button, which will allow Rollbar to post notifications using Slack’s new granular scopes. If you navigate back to the Slack integration in your Project Settings, you will now see the configuration below: If you need help with the setup, do not hesitate to contact us at support@rollbar.com.

January 2022 Grouping Update

This month we are excited to roll out a new January Grouping Update which significantly improves Grouping quality for some of our more relevant SDKs. Mainly PHP, Ruby, Python and Javascript. This update simplifies over 100 Grouping rules within our Grouping rule set by:
  • Reducing overgrouping with new rules placeholders added and an increase of 4.16% in successful new fingerprints
  • Fixing undergrouping by removing generic rules and decrease of 16.36% in the affected fingerprints
Finally, and the most exciting part, these improvements have been rolled out automatically for all accounts with auto-upgrade enabled, so you can focus on fixing bugs while we take care of the squashing effort!

Update regarding Log4j Java vulnerabilities

Rollbar is aware of the Log4j Java vulnerabilities (CVE-2021-44228 and CVE-2021-45046) and we have updated all the potentially impacted infrastructure and we are making updates available for our Java SDK users. We are dedicated to making sure that Rollbar runs quickly and securely within your applications. Learn about how we’ve addressed the Log4J “Log4Shell” zero-day CVE-2021-44228 and CVE-2021-45046

December 2021 Grouping Update

We are pleased to announce our December 2021 Grouping Update that significantly improves grouping coverage and quality for some of our most common SDKs. Java, PHP, and Python issues now have from 2% to 6% higher coverage rates allowing users to discover more bugs and respond to them more quickly. Grouping quality has been improved as well by reducing overgrouping of errors caused by generic rules overwriting more specific ones. Additionally, this release improves our internal pattern standardization for easier rule management. We can continue training our models more efficiently and analyzing millions of crashes to distinguish different error types accurately. Best of all, these improvements have been rolled out automatically for all accounts with auto-upgrade enabled, so you can focus on squashing and fixing bugs!