Skip Navigation
Show nav
Dev Center
  • Get Started
  • Documentation
  • Changelog
  • Search
  • Get Started
    • Node.js
    • Ruby on Rails
    • Ruby
    • Python
    • Java
    • PHP
    • Go
    • Scala
    • Clojure
    • .NET
  • Documentation
  • Changelog
  • More
    Additional Resources
    • Home
    • Elements
    • Products
    • Pricing
    • Careers
    • Help
    • Status
    • Events
    • Podcasts
    • Compliance Center
    Heroku Blog

    Heroku Blog

    Find out what's new with Heroku on our blog.

    Visit Blog
  • Log inorSign up
Hide categories

Categories

  • Heroku Architecture
    • Compute (Dynos)
      • Dyno Management
      • Dyno Concepts
      • Dyno Behavior
      • Dyno Reference
      • Dyno Troubleshooting
    • Stacks (operating system images)
    • Networking & DNS
    • Platform Policies
    • Platform Principles
  • Developer Tools
    • Command Line
    • Heroku VS Code Extension
  • Deployment
    • Deploying with Git
    • Deploying with Docker
    • Deployment Integrations
  • Continuous Delivery & Integration (Heroku Flow)
    • Continuous Integration
  • Language Support
    • Node.js
      • Working with Node.js
      • Node.js Behavior in Heroku
      • Troubleshooting Node.js Apps
    • Ruby
      • Rails Support
      • Working with Bundler
      • Working with Ruby
      • Ruby Behavior in Heroku
      • Troubleshooting Ruby Apps
    • Python
      • Working with Python
      • Background Jobs in Python
      • Python Behavior in Heroku
      • Working with Django
    • Java
      • Java Behavior in Heroku
      • Working with Java
      • Working with Maven
      • Working with Spring Boot
      • Troubleshooting Java Apps
    • PHP
      • PHP Behavior in Heroku
      • Working with PHP
    • Go
      • Go Dependency Management
    • Scala
    • Clojure
    • .NET
      • Working with .NET
  • Databases & Data Management
    • Heroku Postgres
      • Postgres Basics
      • Postgres Getting Started
      • Postgres Performance
      • Postgres Data Transfer & Preservation
      • Postgres Availability
      • Postgres Special Topics
      • Migrating to Heroku Postgres
    • Heroku Key-Value Store
    • Apache Kafka on Heroku
    • Other Data Stores
  • AI
    • Model Context Protocol
    • Vector Database
    • Heroku Inference
      • Inference Essentials
      • AI Models
      • Inference API
      • Quick Start Guides
    • Working with AI
  • Monitoring & Metrics
    • Logging
  • App Performance
  • Add-ons
    • All Add-ons
  • Collaboration
  • Security
    • App Security
    • Identities & Authentication
      • Single Sign-on (SSO)
    • Private Spaces
      • Infrastructure Networking
    • Compliance
  • Heroku Enterprise
    • Enterprise Accounts
    • Enterprise Teams
    • Heroku Connect (Salesforce sync)
      • Heroku Connect Administration
      • Heroku Connect Reference
      • Heroku Connect Troubleshooting
  • Patterns & Best Practices
  • Extending Heroku
    • Platform API
    • App Webhooks
    • Heroku Labs
    • Building Add-ons
      • Add-on Development Tasks
      • Add-on APIs
      • Add-on Guidelines & Requirements
    • Building CLI Plugins
    • Developing Buildpacks
    • Dev Center
  • Accounts & Billing
  • Troubleshooting & Support
  • Integrating with Salesforce
  • Add-ons
  • All Add-ons
  • Honeybadger
Honeybadger

This add-on is operated by Honeybadger Industries LLC

The web developer's secret weapon

Honeybadger

Last updated May 04, 2018

Table of Contents

  • Provisioning the add-on
  • Using with Rails 3.0+
  • Using with Sinatra
  • Using with Rack
  • Confirm configuration
  • Dashboard
  • Migrating between plans
  • Removing the add-on
  • Support
  • Additional resources

Honeybadger is an add-on for tracking and reporting on errors triggered by your applications.

Rather than getting an email every time a user trips the same error in your app (or worse, not even knowing when your users encounter an error), Honeybadger groups every error occurrence by the type of error encountered and notifies you only once per error. You’ll get an email (or a Campfire notice, or a text message) the first time the error occurs.

The goal of Honeybadger is to get your error notifications to you as quickly as possible, and show the error info to you as clearly as possible, so you can fix the problems in your app in no time and delight your customers.

Provisioning the add-on

Honeybadger can be attached to a Heroku application via the CLI:

A list of all plans available can be found here.

$ heroku addons:create honeybadger
-----> Adding honeybadger to sharp-mountain-4005... done, v18

Once Honeybadger has been added a HONEYBADGER_API_KEY setting will be available in the app configuration and will contain the api key that the gem uses to authenticate with the Honeybadger server.

$ heroku config | grep HONEYBADGER_API_KEY
HONEYBADGER_API_KEY    => abc123

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

Using with Rails 3.0+

Ruby on Rails applications will need to add the following entry into their Gemfile specifying the Honeybadger client library.

gem 'honeybadger'

Update application dependencies with bundler.

$ bundle install

That’s it. As long as the HONEYBADGER_API_KEY environment variable is present, Honeybadger should report data in production. Please note that by default Honeybadger does NOT report data in development and test environments.

Using with Sinatra

Using honeybadger in a Sinatra app is just like a Rails app:

# Always require sinatra first.
require 'sinatra'

# Then require honeybadger.
require 'honeybadger'

# Define your application code *after* sinatra *and* honeybadger:

get '/' do
  raise "Sinatra has left the building"
end

Using with Rack

In order to use honeybadger in a non-Rails rack app, just load honeybadger’s configuration and use the Honeybadger::Rack::ErrorNotifier middleware:

require 'rack'

# Load the gem
require 'honeybadger'

# Write your app
app = Rack::Builder.app do
  run lambda { |env| raise "Rack down" }
end

# Configure and start Honeybadger
honeybadger_config = Honeybadger::Config.new(env: ENV['RACK_ENV'])
Honeybadger.start(honeybadger_config)

# And use Honeybadger's rack middleware
use Honeybadger::Rack::ErrorNotifier, honeybadger_config
use Honeybadger::Rack::MetricsReporter, honeybadger_config

run app

Confirm configuration

Configuration of the add-on can be confirmed by running:

$ heroku run honeybadger test

Dashboard

For more information on the features available within the Honeybadger dashboard please see the Honeybadger docs.

The Honeybadger dashboard allows you to configure your notification preferences, including the email address that should be used for sending errors to you, configuration for other notification methods like Campfire, and so on. You can, of course, also use the dashboard to review the errors your app has generated and sent to Honeybadger.

The dashboard can be accessed via the CLI:

$ heroku addons:open honeybadger
Opening honeybadger for sharp-mountain-4005…

or by visiting the Heroku Dashboard and selecting the application in question. Select Honeybadger from the Add-ons menu.

Migrating between plans

Use the heroku addons:upgrade command to migrate to a new plan.

$ heroku addons:upgrade honeybadger:corporate
-----> Upgrading honeybadger:corporate to sharp-mountain-4005... done, v18 ($49/mo)
       Your plan has been updated to: honeybadger:corporate

Removing the add-on

Honeybadger can be removed via the CLI.

This will destroy all associated data and cannot be undone!

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

Support

All Honeybadger support requests should be sent to support@honeybadger.io.

Additional resources

Additional resources are available at:

  • Honeybadger docs

Keep reading

  • All Add-ons

Feedback

Log in to submit feedback.

Zara 4 Hosted Graphite

Information & Support

  • Getting Started
  • Documentation
  • Changelog
  • Compliance Center
  • Training & Education
  • Blog
  • Support Channels
  • Status

Language Reference

  • Node.js
  • Ruby
  • Java
  • PHP
  • Python
  • Go
  • Scala
  • Clojure
  • .NET

Other Resources

  • Careers
  • Elements
  • Products
  • Pricing
  • RSS
    • Dev Center Articles
    • Dev Center Changelog
    • Heroku Blog
    • Heroku News Blog
    • Heroku Engineering Blog
  • Twitter
    • Dev Center Articles
    • Dev Center Changelog
    • Heroku
    • Heroku Status
  • Github
  • LinkedIn
  • © 2025 Salesforce, Inc. All rights reserved. Various trademarks held by their respective owners. Salesforce Tower, 415 Mission Street, 3rd Floor, San Francisco, CA 94105, United States
  • heroku.com
  • Legal
  • Terms of Service
  • Privacy Information
  • Responsible Disclosure
  • Trust
  • Contact
  • Cookie Preferences
  • Your Privacy Choices