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 support@rollbar.com or a message via the in-app chat.

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 support@rollbar.com or a message via the in-app chat.

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

Syntax:

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:

SELECT
  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,
  COUNT(*)
FROM item_occurrence
WHERE framework = 'browser-js'
  AND timestamp > unix_timestamp() - 3600
GROUP BY 1
ORDER BY 1

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/executor.py 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 support@rollbar.com 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 support@rollbar.com or a message via the in-app chat.

Occurrences from Android applications contain stack frames from the Android framework itself. Different Android versions and distributions can have some minor variations in the entry frames. We’ve now released a migration that upon activation will recognize a number of these variations and group related occurrences together.

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

We recommend activating this migration for all Android projects. However, note that grouping migrations are not retrospective so you may receive some 'New Item' notifications initially.

Additionally, this option is activated by default for all new projects and it 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.

If you’re using C#, you now have the option to exclude file names from the strings used for fingerprinting.

This option is enabled by default which means that we’ll take into account both the file name and the method of stack frames when fingerprinting. If you disable this option, we’ll only include the method. Please note that in the case of C#, the method contains the fully qualified class name, method name, and method signature, so disabling this option has a very low risk of overgrouping.

You can find this option by going to Settings>Setup>Custom Fingerprinting.

In case you want to exclude file names from multiple projects, you should disable this option in each project.

Please be aware that grouping changes are not retrospective. Disabling this option will cause your new errors to be grouped differently than before which will generate an initial flurry of 'New Item' notifications.

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 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.