You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi there! I was wondering if there's any accepted way to configure Raygun to do its logging in an out-of-band process, like an ActiveJob worker. A cursory glance at lib/raygun.rb suggests it wouldn't be too hard to monkey-patch that kind of thing in, but I don't want to reinvent anything that's already on a roll. Thanks in advance for your help!
The text was updated successfully, but these errors were encountered:
Nope, there's nothing at the moment. Part of the rationale would be to limit the number of components involved in error reporting (e.g if there's a Redis connection error and you're using a Resque/Sidekiq backend, you'll end up hitting failsafe rather than reporting)
Having said that, I'd be more than happy to accept an ActiveJob compatible patch - perhaps a config setting that accepts async_reporting_backend = :active_job or similar? Keeping in mind that we still need to support Rails versions that don't contain ActiveJob.
Hi there! I was wondering if there's any accepted way to configure Raygun to do its logging in an out-of-band process, like an ActiveJob worker. A cursory glance at
lib/raygun.rb
suggests it wouldn't be too hard to monkey-patch that kind of thing in, but I don't want to reinvent anything that's already on a roll. Thanks in advance for your help!The text was updated successfully, but these errors were encountered: