Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Asynchronous issue reporter? #66

Closed
phyllisstein opened this issue May 3, 2015 · 3 comments
Closed

Asynchronous issue reporter? #66

phyllisstein opened this issue May 3, 2015 · 3 comments

Comments

@phyllisstein
Copy link

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!

@nikz
Copy link
Contributor

nikz commented May 4, 2015

Hi there!

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.

Feel free to ping me if you need any help :)

Thanks!

Nik

@phyllisstein
Copy link
Author

That makes sense. I'll try to find the time to submit the PR you suggested, instead of just hacking something in locally. Thanks Nik!

@nikz
Copy link
Contributor

nikz commented May 5, 2015

No worries - even if you just hack something and submit it we can work together to get it merged in.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants