Deploy Tracking

Having issues deploy tracking in your app? Check the deploy troubleshooting doc.

Why track deploys?

Deploy Tracking with Airbrake gives insight into the relationship between your deploys and your errors. Here are a few of the benefits deploy tracking gives you:

  • Resolve all errors on a deploy
  • Project and error graphs show deploy markers
  • Insight into which deploys introduced problems
  • Insight into which deploys solved problems
  • Generate backtrace links to click through to the offending lines of code
  • Filter errors by deploy

Resolve all errors on a deploy

Triggering a deploy in your Airbrake project resolves all errors in the specified environment this gives you a fresh slate each deploy so you can tell which errors you fixed and which errors are still an issue.

Deploys show on your project’s error graphs

Deploys are marked with blue circles on your project’s graphs graph with deploys

Hovering over them will activate a tooltip with environment and timestamp information.

Using deploy tracking creates helpful links in your backtrace so you can click through to the file/line/revision in GitHub/GitLab.

backtrace link to github

Filter errors by deploy

You can see your deploy activity on your project overview page and you can filter by a specific deploy in the search dropdown.

filter by deploy

Deploy tracking with the API

You can track a deploy with the POST to the /v4/deploys api endpoint docs.

You want to trigger a POST each time you deploy, specifying at least your PROJECT_ID, PROJECT_KEY and environment in the JSON data. If you provide the other keys this will enable us to build links in backtraces that link to your repository.

Example curl command

curl -X POST -H "Content-Type: application/json" -d '{"environment":"production","username":"john","repository":"","revision":"38748467ea579e7ae64f7815452307c9d05e05c5","version":"v2.0"}' ""

Example bash script

This is a simple example that registers a deploy with Airbrake. It assumes it is run from a Git repository of your deployed project code. You can tweak how the deployed REVISION is determined to suite your deploy process. Make sure you check and modify the variables as appropriate for your project and requirements.


REVISION="$(git rev-parse HEAD)"

curl -X POST \
  -H "Content-Type: application/json" \
  -d "{'environment':'${ENVIRONMENT}','username':'${USERNAME}','repository':'${REPOSITORY}','revision':'${REVISION}'}" \

JSON post data description

You can post JSON data with the following keys. there are example

Key Example
environment production
username john
revision 38748467ea579e7ae64f7815452307c9d05e05c5
version v2.0


The API returns 201 Created status code on success.

Deploy tracking with rake airbrake:deploy

Deploy tracking requires the latest airbrake notifier. Be sure you have the latest version installed from github.

Once installed, your application will have a new rake task, here are some examples.

To Mark all Errors as Resolved for the production environment you can use the following command:

rake airbrake:deploy TO=production

To Mark all Errors as Resolved for a specific environment, use the following format:

rake airbrake:deploy RAILS_ENV=<rails environment> TO=rails environment

For example the following rake command will track a deploy to the development environment.

rake airbrake:deploy RAILS_ENV=development TO=development


If you use capistrano, you shouldn’t have to run the rake command by hand. The Airbrake notifier also includes a capistrano recipe that runs after deploy:cleanup which automatically triggers that rake task.

DEPRECATED Airbrake executable

DEPRECATION WARNING: The information on the Airbrake executable is related to Airbrake v4 only and is no longer available in Airbrake v5.

airbrake deploy -k YOUR_API_KEY

For more information about the executable, please visit the Airbrake gem wiki pages.

Usage Engine Yard Cloud

To notify Airbrake of your deploys to EngineYard cloud, you can use the following deploy/after_restart.rb script:

def notify_airbrake?(config)
  %w(staging production integration).include?(config.environment_name) &&
  %w(solo app_master).include?(config.current_role)

def track_deploy(config)
    "cd #{config.current_path} && bundle exec rake airbrake:deploy " \
    "ENVIRONMENT=#{config.environment_name} REVISION=#{config.active_revision} " \
    "USERNAME=#{config.deployed_by} REPOSITORY=#{config.repo}"

track_deploy(config) if notify_airbrake?(config)

You can find more info on config and its variables in the EngineYard doc on ruby deploy hooks.