honeybadger-ruby
                                
                                
                                
                                    honeybadger-ruby copied to clipboard
                            
                            
                            
                        Ruby gem for reporting errors to honeybadger.io
Closes https://github.com/honeybadger-io/honeybadger-ruby/issues/416 Error reporter [API doc](https://api.rubyonrails.org/v7.1/classes/ActiveSupport/ErrorReporter.html#method-i-subscribe) Re the `source` parameter (new in v7.1): - Added a new config option so users can automatically ignore certain sources - Only (two internal...
Closes #383 Makes use of the Railtie `before_initialize` hook, which has been around [for a while](https://github.com/rails/rails/commit/3afdfc35e8aec7e6379e093dd1278cb3de54f21b). `before_initialize` runs after Rails' config and application has booted, but before the framework initializers...
The default Ruby fingerprint is calculated server-side in our processing pipeline. Users can [customize the fingerprint](https://docs.honeybadger.io/lib/ruby/getting-started/customizing-error-grouping/) client-side using `before_notify` filter. This works fine for users who want to control grouping...
See https://github.com/rails/rails/pull/43625 Interface: ```ruby Rails.error.handle do 1 + '1' # raises TypeError end 1 + 1 # This will be executed Rails.error.record do 1 + '1' # raises TypeError end...
https://github.com/honeybadger-io/honeybadger-ruby/blob/1052fd6ab7d9d5a138bd9d1f64c4a077bf980193/lib/honeybadger/agent.rb#L121 Should probably be `def notify(exception_or_opts, **opts)`.
Idea: initialize Honeybadger before running other Rails initializers. In addition to catching more errors, this allows errors in initializers to be reported with the correct config (such as config.env, which...
See #296 for additional context. Currently, the `logging.level` setting only works when `logging.path` (or a custom logger) is also configured. It would be nice if `logging.level` also applied to the...
While Rails [generally recommends](https://edgeguides.rubyonrails.org/active_job_basics.html#job-execution) that you don't use the default in-memory ActiveJob backend (async?) in production, it would be nice if we could support it for those who do.
We had a request for logging errors during test runs. Per this conversation (via @ioquatix): https://twitter.com/ioquatix/status/1318312887547408384 One way we could solve this is to add another backend option, perhaps a...