Skip Navigation
Show nav
Heroku Dev Center
  • Get Started
  • Documentation
  • Changelog
  • Search
  • Get Started
    • Node.js
    • Ruby on Rails
    • Ruby
    • Python
    • Java
    • PHP
    • Go
    • Scala
    • Clojure
  • 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
View categories

Categories

  • Heroku Architecture
    • Dynos (app containers)
    • Stacks (operating system images)
    • Networking & DNS
    • Platform Policies
    • Platform Principles
  • Command Line
  • Deployment
    • Deploying with Git
    • Deploying with Docker
    • Deployment Integrations
  • Continuous Delivery
    • Continuous Integration
  • Language Support
    • Node.js
    • Ruby
      • Working with Bundler
      • Rails Support
    • Python
      • Background Jobs in Python
      • Working with Django
    • Java
      • Working with Maven
      • Java Database Operations
      • Working with the Play Framework
      • Working with Spring Boot
      • Java Advanced Topics
    • PHP
    • Go
      • Go Dependency Management
    • Scala
    • Clojure
  • Databases & Data Management
    • Heroku Postgres
      • Postgres Basics
      • Postgres Performance
      • Postgres Data Transfer & Preservation
      • Postgres Availability
      • Postgres Special Topics
    • Heroku Redis
    • Apache Kafka on Heroku
    • Other Data Stores
  • Monitoring & Metrics
    • Logging
  • App Performance
  • Add-ons
    • All Add-ons
  • Collaboration
  • Security
    • App Security
    • Identities & Authentication
    • Compliance
  • Heroku Enterprise
    • Private Spaces
      • Infrastructure Networking
    • Enterprise Accounts
    • Enterprise Teams
    • Heroku Connect (Salesforce sync)
    • Single Sign-on (SSO)
  • 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
  • Add-ons
  • All Add-ons
  • RuntimeError
RuntimeError

This add-on is operated by Devels Advocates LLP

Track and manage your runtime errors directly in Github

RuntimeError

Last updated 13 October 2015

Table of Contents

  • 1. Provisioning the add-on
  • 2. Configure the add-on
  • 3. Installing
  • Removing the add-on
  • Support

RuntimeError is an add-on for tracking and managing your runtime errors directly in Github.

Track errors in your web application. Your team is notified when errors happen. Manage your errors from your existing project management tools. Don’t waste time recreating bug reports.

1. Provisioning the add-on

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

$ heroku addons:create runtimeerror:test
-----> Adding runtimeerror to sharp-mountain-4005... done, v18 (test)

Once RuntimeError has been added a RUNTIMEERROR_EMAIL setting will be available in the app configuration and will contain the runtimeerror email is used to route errors to the correct the Github project. This can be confirmed using the heroku config:get command.

$ heroku config:get RUNTIMEERROR_EMAIL
hero+ku+hello-world@runtimeerror.net

2. Configure the add-on

Once you’ve added the add-on, you’ll need to point to your Github repository. Do this through the configuration panel on Dashboard. You can access this in two ways. You can use the CLI:

$ heroku addons:open runtimeerror

Or you can click through from your app dashboard, into the RuntimeError add-on, and choose your Github repository you want for managing Issues.

Your application is now configured to fully integrate with the add-on.

3. Installing

Rails

Add the following entry into Gemfile

gem 'runtimeerror_notifier'

Update application dependencies with bundler.

$ bundle install

Finally, initialize the project with a standard config

  1. Either using the rails generator,
rails generate runtimeerror_notifier:install
  1. Or by manually creating config/initializers/runtimeerror_notifier.rb file with the content below
  if defined?(RuntimeerrorNotifier)
    RuntimeerrorNotifier.for ENV['RUNTIMEERROR_EMAIL']
    RuntimeerrorNotifier::Notifier::IGNORED_EXCEPTIONS.push(*%w[
      ActionController::RoutingError
    ])
  end

Removing the add-on

RuntimeError can be removed via the CLI.

This will destroy all associated data and cannot be undone!

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

Support

All RuntimeError support and runtime issues should be submitted to RuntimeError Support

Keep reading

  • All Add-ons

Feedback

Log in to submit feedback.

Ziggeo Scout APM

Information & Support

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

Language Reference

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

Other Resources

  • Careers
  • Elements
  • Products
  • Pricing

Subscribe to our monthly newsletter

Your email address:

  • RSS
    • Dev Center Articles
    • Dev Center Changelog
    • Heroku Blog
    • Heroku News Blog
    • Heroku Engineering Blog
  • Heroku Podcasts
  • Twitter
    • Dev Center Articles
    • Dev Center Changelog
    • Heroku
    • Heroku Status
  • Facebook
  • Instagram
  • Github
  • LinkedIn
  • YouTube
Heroku is acompany

 © Salesforce.com

  • heroku.com
  • Terms of Service
  • Privacy
  • Cookies