Exceptions not sent to Sentry from development environment (better_errors)

[shrirambalakrishnan]

In development environment, only when exception is captured explicitly using Raven.capture, the exception is getting sent to Sentry and shown in the list of exceptions.

But if config.consider_all_requests_local = false in development.rb, the exceptions are sent.

Related issue - https://github.com/getsentry/raven-ruby/issues/202

Gem versions:
rails-4.2.7.1
sentry-raven-2.6.2

[nateberkopec]

I'm going to need some additional reproduction steps. Using a blank "rails new" application in development (so config.consider_all_requests_local = true), I can successfully raise and capture exceptions w/Sentry, e.g.:

class HelloController < ApplicationController
  def exception
    raise "Hi!"
  end
end

[nateberkopec]

You can try modifying this script to reproduce your issue.

[irobayna]

@nateberkopec Same here with an Ruby on Rails API, I do see upon startup

INFO -- sentry: ** [Raven] Raven 2.6.3 ready to catch errors

specs:

Rails 5.1.3
Puma 3.9.1
Ruby 2.4.1-p111

BTW, if I send a command to capture message that works:

Raven.capture_message("Something went very wrong")

Your example above does not...

[nateberkopec]

Please feel free to reopen with reproduction steps.

[d1ceward]

I have same problem and for me it's caused by better_errors gem.

Simply add better_errors gem to your script to reproduce.

[punitcse]

I also have the same issue using
rails 5.2
sentry-raven-2.7.4

[kerwin-personalyze]

Hi, I also encountered the same issue.
I don't have better_errors gem in my project.

What I did was to declare this in my controller

      def index
        1/0
      end

and have the following set in my sentry.rb

Raven.configure do |config|
  config.dsn = *******
  config.sanitize_fields = Rails.application.config.filter_parameters.map(&:to_s)
  config.environments = %w[development]
  config.excluded_exceptions = []
end

If I invoke Raven.send_capture(), then it works.