Read more

Sending errors to sentry from development

Emanuel
April 20, 2017Software engineer at makandra GmbH

For the initial setup or changes in the sentry reporting it might be useful to enabled reporting of sentry in development. Don't commit these changes and prefer to report to the staging environment. As other developers might be confused of these errors try to given them a proper message and delete them afterwards.


  1. Add config.raven_dsn = 'your-dns' in config/environments/development.rb.
  2. Add development to existing environments in the Raven.configure block: config.environments = ['development', 'staging', 'production'].
  3. Remove better_errors from Gemfile if existing and bundle.

Illustration online protection

Rails Long Term Support

Rails LTS provides security patches for old versions of Ruby on Rails (2.3, 3.2, 4.2 and 5.2)

  • Prevents you from data breaches and liability risks
  • Upgrade at your own pace
  • Works with modern Rubies
Read more Show archive.org snapshot

With Raven.capture_message('Test from development') you can test your setting on console. Raising an exception will now report to sentry. You can see this in the log:

INFO -- sentry: ** [Raven] Sending event c49343eec8argefb8bcasd193103244a to Sentry
Posted by Emanuel to makandra dev (2017-04-20 11:50)