-
Notifications
You must be signed in to change notification settings - Fork 174
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
Fix Sidekiq metadata: Ensures metadata is attached to notifications #495
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lib changes look fine, but would it make sense to have tests in spec/integrations/sidekiq_spec.rb that checks whether Sidekiq request data is cleared or not depending on various conditions after calling Bugsnag::Sidekiq#call
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
possible suggestion, otherwise lgtm
Just need the codeclimate allowable complexity to be updated here, I don't have access to that functionality. |
@kattrali can you make the change? |
I see this includes a metadata tab for errors that occur within Sidekiq, but only includes msg and queue. Is there a way for Bugsnag to report the worker args when any error occurs within Sidekiq? |
Hey @javierjulio, the arguments for the job the worker was running with should be present in the |
@Cawllec no everything is good. 👏🏻 Thanks so much for fixing this! ❤️ I confirmed the fix in development by replicating various errors from production and am now seeing the Sidekiq data in all those cases where we weren't before. |
Goal
Fix the issue where the Sidekiq integration is clearing request data before it can be attached to a notify call.