Sinatra integration guide

Add Bugsnag to your Sinatra and Padrino projects.

Installation

Add the bugsnag Ruby gem to your Gemfile:

gem 'bugsnag'

Don’t forget to run bundle install after updating your Gemfile.

Basic configuration

To identify your app in the Bugsnag dashboard, you’ll need to configure your Bugsnag API key. You can find your API key when creating a project in your Bugsnag dashboard, or later from your project settings page.

To set your API key in your Sinatra app, add the following code to your config.ru file:

require 'bugsnag'

Bugsnag.configure do |config|
  config.api_key = 'YOUR_API_KEY_HERE'
end

Alternatively, you can set the BUGSNAG_API_KEY environment variable.

If you’d like to configure Bugsnag further, check out the configuration options reference.

Reporting unhandled exceptions

To automatically capture unhandled exceptions, you’ll need to enable the Bugsnag Rack middleware:

use Bugsnag::Rack

set :raise_errors, true
set :show_exceptions, false

At this point, Bugsnag should be installed and configured, and any unhandled exceptions will be automatically detected and should appear in your Bugsnag dashboard.

Note: If you wish to use custom error handlers in your app, then you need to notify Bugsnag explicitly.

error 500 do
  Bugsnag.auto_notify($!)
  erb :'errors/500'
end

Reporting handled exceptions

Reporting handled exceptions can be accomplished as follows:

begin
  raise 'Something went wrong!'
rescue => exception
  Bugsnag.notify(exception)
end

Adding diagnostics or adjusting severity

It can often be helpful to adjust the severity or attach custom diagnostics to handled exceptions. For more information, see reporting handled errors.

Sending diagnostic data

Automatically captured diagnostics

As well as a full stacktrace for every exception, Bugsnag will automatically capture the following diagnostic data:

  • Request information, including ip, headers, URL, HTTP method, and HTTP params
  • Release stage (production, beta, staging, etc)
  • Hostname

Custom diagnostics

In order to quickly reproduce and fix errors, it is often helpful to send additional application-specific diagnostic data to Bugsnag. This can be accomplished using a before notify callback as follows:

Bugsnag.before_notify_callbacks << lambda {|notification|
  notification.add_tab(:diagnostics, {
    product: current_product.name
  })
}

For more information, see the customizing error reports reference.

Identifying users

In order to correlate errors with customer reports, or to see a list of users who experienced each error, it is helpful to capture and display user information on your Bugsnag dashboard.

You can set this information using a before notify callback as follows:

Bugsnag.before_notify_callbacks << lambda {|notification|
  notification.user = {
    email: current_user.email,
    name: current_user.name,
    id: current_user.id
  }
}

For more information, see reporting handled errors.

Tracking deploys

By sending your source revision or application version to us when you deploy a new version of your app, you’ll be able to see which deploy each error was introduced in, or seen in.

If you are using Capistrano, notify Bugsnag of your deploys by adding our integration to your Capfile:

require 'bugsnag/capistrano'
set :bugsnag_api_key, 'api_key_here'

If you are using a deployment system other than Capistrano, see our deploy tracking guide.

Catching JavaScript errors

Catch and report errors in your client-side JavaScript with the Web browser JavaScript guide