-
-
Notifications
You must be signed in to change notification settings - Fork 503
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
Exceptions from ActiveJob with Resque backend are not captured on Sentry #1559
Comments
I'm not able to reproduce this issue with the example app under With
|
Explicitly sending a message works both from rails console or from with the job's I will try to reproduce in a sample app and push that. |
Here is the test app: https://github.com/tsrivishnu/rails-sentry-resque-active-job-test. I included instructions to run it in docker with docker-compose. Let me know if you face any issues. Correction to my previous comment. |
@tsrivishnu ok it's because resque worker doesn't contain either I think you can make it work by adding I'll make a PR to change the default environment to |
@st0012 Thank you. I confirm that it works after adding Feel free to close this issue or keep it open for you to track the PR to change the default environment to 'development'. |
Describe the bug
Exceptions from ActiveJob jobs are not sent to Sentry. The jobs simply fail and no errors are sent to Sentry.
I'm not sure if I'm missing any configuration options for this to work correctly.
To Reproduce
$ bundle exec rake environment resque:work QUEUE=*
Expected behavior
foo
RuntimeError is captured and sent to SentryActual behavior
foo
RuntimeError is not captured and not sent to SentryEnvironment
Sentry Config
The text was updated successfully, but these errors were encountered: