Announcing our new Java Spring SDK

Rollbar now supports Spring through our new Java Spring SDK. You can iterate and release even faster with the libraries you already use by integrating Rollbar with existing Spring applications.

  • Exceptions raised by Spring are handled automatically by Rollbar
  • See relevant code context with telemetry, local variables, stack traces, and git blame
  • SDK includes example integrations for Spring Boot and MVC

Get the SDK from the "rollbar-java" repo on GitHub and more details are on the blog, "Introducing our new Java Spring Error Monitoring SDK"

Introducing June 2020 Grouping Update

We’re excited to announce the June 2020 Grouping Update. This is the first versioned update and replaces Grouping Migrations. It contains all existing grouping improvements in one package. Going forward versioned Grouping Updates simplify getting the most accurate grouping with one click.

With a single click you get:

  • Improved algorithm for grouping Browser JavaScript errors
  • Improved algorithm for grouping Android errors
  • React.js Error Message Unminification
  • Missing jQuery recognition
  • JavaScript Source Maps translations with untangled method names
  • Recursive call chain recognition
  • Improved data scrubbing
  • Grouping by scrubbed exception message of traces without frames
  • Ruby message pattern recognition

Don’t forget to enable auto-upgrade to be the first to get the most accurate grouping every time we update it!

To activate it go to Settings -> Setup -> Upgrade Grouping

Introducing Ruby message pattern recognition

We're still excited! This time about beefing up our default grouping algorithm to significantly improve the observability of errors caused by 25% of Ruby software crashes. Our algorithm now recognizes well known exception messages and computes the fingerprint from the valuable data in those messages. This improvement is an important milestone in our automated error response roadmap.

To activate this enhancement on existing projects go to Settings → Advanced → Migrations. Otherwise, this is already enabled by default on newly created projects.

To see a list of these exception messages, please see the Ruby message patterns docs.

To activate the improvements on existing projects go to Settings → Advanced → Migrations. For new projects we activate them automatically.

Introducing the Rollbar Deploy GitHub Action

We’re excited to announce our support for GitHub Actions with our new Rollbar Deploy GitHub Action. Teams using GitHub Actions for building their CI/CD pipeline can now easily send deploy information to Rollbar and respond to any new errors quickly.

With this action, you'll be able to -

  • Automatically notify Rollbar of any new deploys from GitHub Actions
  • Easily link deploy information to new versions to gain visibility into the changes being deployed, the person deploying the changes, the environment impacted, and the new errors that are being generated
  • Respond to errors with detailed code context

To start using this GitHub Action, go here. For the best user experience, we recommend using our GitHub integration as well.

Questions? Feedback? Let us know what you think by sending an email to or a message via the in-app chat.

Introducing Grouping Enhancements

We're excited to introduce two new grouping enhancements that will reduce noise and improve the observability of errors:

  • Reduced noise: the improved algorithm performs 10-40% better on grouping redundant occurrences.
  • Better observability: the new algorithm uses the message for exceptions without stack frames to group in order to ensure that any truly unique errors are exposed.

To activate the enhancements on existing projects go to Settings → Advanced → Migrations. The enhancements are enabled by default on new projects.

To read more about this release, please see the grouping docs.

Introducing Git Blame Support for GitHub Integration


We're excited to introduce Git Blame for GitHub - to help you identify the last person to write or edit the line of code that caused the error, directly within the Rollbar UI.

In a nutshell, you can:

  • See who the last author was to edit the line of code that caused the error
  • Correlate when the code was written to the date and time of the item occurrence to help triage the error
  • Get context on the history of the code and why, how the code was added
  • Assign the error to the last author if needed

To integrate GitHub, go here.

To read more about this feature release, go here.

Introducing the new Rollbar UX

We're excited to introduce the new Rollbar user experience. We hope you like it as much as we’ve enjoyed building it for you! Here are some things to try:

  • Monitor all microservices with one tool in one view. We've adopted powerful and consistent multi-project views across the entire user workflow. Get intelligent, real-time alerts on errors across microservices in a single view using our new multi-project filter. Whether you’re looking at the main dashboard, the Items view, or Versions, you’ll only see what you care about.

  • Debug faster with a consistent workspace and powerful filters. Users now have their own personal workspace with powerful filters for projects, environments, and frameworks that persist across all views. Finding new errors is also faster and easier with improved Timeframe and ‘New or Reactivated’ filters.

  • Get insights on data across multiple projects in one go. Run queries and correlate data across services with the multi-project functionality in RQL. Visualize the results and look for trends or anomalies easily with graphs.

For more information on how to switch to the new UX, head to our docs.

Questions? Feedback?

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

Integration with Azure DevOps Issue Tracking

You can now create and resolve Work Items in Azure DevOps directly from Rollbar, making error monitoring and debugging even faster. No more switching between multiple tools and adding information manually!

With this integration, you can:

  • Create an Azure DevOps Work Item directly from Rollbar, either directly or based on the ruleset (details below)
  • View the stack trace in the Azure DevOps Work Item
  • Auto-create tags and area paths, and view the Item in Rollbar with a single click
  • Change the Work Item state automatically based on changes in Rollbar
  • Resolve Azure DevOps Work Item automatically once resolved in Rollbar

For more information on the integration and instructions on setting it up, check out our integration guide here.

Questions? Feedback?

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

IF function in RQL

You can now write more complex queries in RQL using the new IF function.


IF(bool_expr, value_if_true, value_if_false)

For example, to chart Javascript error occurrences based on whether they happened immediately upon page load, shortly after load, a while after load, or long after load, you can use IF with the client.runtime_ms property as follows:

  IF(client.runtime_ms < 1000, '1_load_to_1second',
    IF(client.runtime_ms < 60*1000, '2_1second_to_1minute',
      IF(client.runtime_ms < 60 * 60 * 1000, '3_1minute_to_1hour',
        IF(client.runtime_ms >= 60 * 60 * 1000, '4_1hour_and_up', 'unknown')))) time_on_page,
FROM item_occurrence
WHERE framework = 'browser-js'
  AND timestamp > unix_timestamp() - 3600

Screenshot 2019-07-05 12.15.50.png

Use regex to configure your file paths for better grouping (beta)

Due to popular demand, you can now customize your file path with regex rules.

Differences in file paths often result in multiple items being created which lead to noisy item lists. If you run into this problem, there is now a solution - define regex rules to replace certain patterns of your file path with a common replacement.

For example, a file path such as /var/www/core3/releases/20190225T150625/src/services/automation/ will change every time there is a new release due to different timestamps.

To avoid creating new items, you can go to Settings>Setup>Custom Fingerprinting and define a new regex rule under File Path Canonicalization.


This rule will create a new item in your list that generalizes file paths matching this pattern and therefore group occurrences more accurately.

We are currently looking for beta testers to try out this feature! If you’re interested, send us an email to or get in touch via the in-app chat. Please note that the option will only be available if we enable it for you.

You can learn more about this feature in the docs.

Questions? Feedback?

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