This add-on is operated by Rollbar

Real-time, cross-platform crash reporting and error logging starting at $0/mo

Last updated March 13, 2025

This article explains how to provision, configure, and remove the Rollbar add-on for Heroku.

Provisioning the Rollbar add-on

Rollbar can be added to a Heroku application via the CLI:

$ heroku addons:create rollbar:trial-5k -a myapp-production

Creating rollbar:trial-5k on ⬢ myapp-production... trial-5k
Created rollbar-clean-85894 as ROLLBAR_ACCESS_TOKEN, ROLLBAR_ENDPOINT
Use heroku addons:docs rollbar to view documentation

A list of all plans available can be found here.

Once Rollbar has been added, a ROLLBAR_ACCESS_TOKEN setting will be available in the app configuration and will contain your server-side access token. This can be confirmed using the heroku config:get command.

$ heroku config:get ROLLBAR_ACCESS_TOKEN

a1a1b2b2c3c3d4d4e5e5f6f6e7e7d8d8

After installing Rollbar the application should be configured to fully integrate with the add-on.

Attach Rollbar to Multiple Apps

If you are using Heroku Pipelines for a continuous delivery workflow, then we recommend the following configuration:

• First create the Rollbar add-on on your production app (see the previous section);
• Then attach the same Rollbar add-on to the other apps in the pipeline.

To attach the same Rollbar add-on to multiple apps, first determine the add-on name:

$ heroku addons

Owning App        Add-on               Plan          Price     State
----------------  -------------------  ------------  --------  --------
myapp-production  rollbar-clean-85894  rollbar:trial-5k  free      created

Then use the addons:attach command to attach it to additional to additional apps:

$ heroku addons:attach rollbar-clean-85894 -a myapp-staging

Attaching rollbar-clean-85894 to ⬢ myapp-staging... done
Setting ROLLBAR config vars and restarting ⬢ myapp-staging... done, v3

Exception data from each app to which you attached the add-on will be sent to the same Rollbar project. We recommend to configure a different environment value for each app so you can differentiate between exceptions from production, staging, etc.

Local setup

Environment setup

After provisioning the add-on, it’s necessary to locally replicate the config vars so your development environment can operate against the service.

Though less portable, it’s also possible to set local environment variables using export ROLLBAR_ACCESS_TOKEN=value.

Use Foreman to configure, run and manage process types specified in your app’s Procfile. Foreman reads configuration variables from an .env file. Use the following command to add the ROLLBAR_ACCESS_TOKEN values retrieved from heroku config to .env.

$ heroku config -s | grep ROLLBAR_ACCESS_TOKEN >> .env
$ more .env

For more information, see the Heroku Local article.

For detailed information about how to configure and use the different client libraries, please head over to Rollbar’s docs.

Dashboard

For more information on the features available within the Rollbar dashboard please see the docs at rollbar.com/features.

The dashboard can be accessed via the CLI:

$ heroku addons:open rollbar

or by visiting the Heroku apps web interface and selecting the application in question. Select Rollbar from the Add-ons menu.

Migrating between plans

Use the heroku addons:upgrade command to choose a new plan. This is a downtime-free operation.

$ heroku addons:upgrade rollbar:essentials-30k

Upgrading rollbar:essentials-30k to sharp-mountain-4005... done, v18 ($19.00/mo)
Your plan has been updated to: rollbar: essentials-30k

Removing the Rollbar add-on

Rollbar can be removed via the CLI.

$ heroku addons:destroy rollbar
-----> Removing rollbar from sharp-mountain-4005... done, v20 (free)

Support

All Rollbar support and runtime issues should be submitted via on of the Heroku Support channels. Any non-support related issues or product feedback is welcome at support@rollbar.com.