Rollbar changelog rollbar.com

Since we introduced error merging a few months ago, one of the most common requests we've received is to allow for merging all items that match a search. We're happy to announce that this feature has been launched!

Any time you click the checkbox to select all items on the current page, you'll be presented with an option to select all matching items across all pages so you can edit or merge them.

Try it out and let us know what you think!

Following our recent introduction of support for Node.js on AWS Lambda, we've extended our Lambda support to include Python too.

For full details on how to integrate pyrollbar into your Lambda environment, check out our AWS Lambda docs.

We're excited to introduce support for authentication via Google OAuth. If any of the email addresses for your user are Google accounts (either personal GMail or G Suite), then you can log in with Google to access your account more quickly.

We've updated rollbar.js to include a new lambdaHandler convenience function that abstracts away some of the necessary steps for making rollbar.js work in Lambda and adds additional contextual information from the Lambda environment to the error report.

For full details, check out our rollbar.js docs.

We've added a couple of easier ways to scrub input data that is collected and transmitted to Rollbar as part of our recently-introduced Javascript Telemetry feature:

• By setting scrubTelemetryInputs:true in the Rollbar configuration, all user input data will be omitted from telemetry
• For finer-grained input scrubbing, you may define a function telemetryScrubber that will be automatically called every time an input event is detected and will determine if the input data should be scrubbed or not.

Telemetry scrubbing is included as part of our latest v2.2.7 release.

For full details, check out the rollbar.js docs.

The latest release of rollbar.js introduces Telemetry, a powerful tool that can help you understand and fix critical exceptions more quickly.

Telemetry provides a series of 'breadcrumbs' that occurred prior to an exception, including user actions, network calls, and console messages. You can even see other exceptions that occurred on the same page and quickly pull them up in another browser window!

To start collecting telemetry data, simply update to the latest release of rollbar.js and re-deploy your app.

Let us know if you have feedback or questions!

We've updated our JIRA integration to use OAuth to authenticate Rollbar users when creating and updating JIRA issues. For instructions on configuring JIRA to accept connections from Rollbar, check out our JIRA guide.

Existing connections to JIRA via Basic authentication will continue to work, but new connections must be made via OAuth.

We've also added an option so that any user in a project can create a JIRA issue using the default credentials for the project.

Previously, every user had to connect to JIRA before they could create an issue.

Question or comments on these improvements? Just message us via the in-app chat or via support@rollbar.com.

We've released encryption at rest, an advanced security feature included in the Compliant SaaS edition of Rollbar.

We encrypt all raw data using AES256-GCM at the application level, and each project within an account gets its own key. This approach is superior to disk-based encryption.

When you have encryption at rest enabled, you can see in the settings when the feature was activated and when the historical data encryption was completed for each project:

Contact us to upgrade to Compliant SaaS and enable this feature for your account.

Rollbar's source map support has been improved to display original Javascript method names as well as file names and line numbers when a source map is applied to a stack trace.

This improvement is automatically enabled for all new projects.

For existing projects:

This change will cause items to have a different fingerprint, so it is not enabled by default. To turn on this feature, go to Settings --> Migrations and check the corresponding option:

You can configure your Rollbar projects to set all items to Resolved each time you deploy to an environment.

We've updated this feature to automatically mark items to be resolved in the Revision specified in the deploy, which helps provide a more accurate history of which code changes fixed which errors.

Enable auto-resolve on deploy (via Settings --> Deploys):

Report a deploy:

curl 'https://api.rollbar.com/api/1/deploy/' -F revision=122f7da -F environment=production -F access_token=abcdef1234 

Items are automatically resolved in the deployed revision: