After upgrading raven-ruby from an ancient version to the latest version, the only context we get for exceptions raised by workers is Sidekiq, greatly reducing the usefulness the list view (lots of errors look the same). Basically, all our worker errors are generic stuff like:

whereas before we used to have the file name of the template where the exception was raised.
I've been digging around and it seems like https://github.com/getsentry/raven-ruby/blob/master/lib/raven/integrations/sidekiq.rb#L48 might be missing the case of wrapped jobs, in which case
context["job"]["wrapped"]
contains at least the job class name (in this case MailJob), which would already be a huge improvement over simply Sidekiq.
After upgrading
raven-rubyfrom an ancient version to the latest version, the only context we get for exceptions raised by workers isSidekiq, greatly reducing the usefulness the list view (lots of errors look the same). Basically, all our worker errors are generic stuff like:whereas before we used to have the file name of the template where the exception was raised.
I've been digging around and it seems like https://github.com/getsentry/raven-ruby/blob/master/lib/raven/integrations/sidekiq.rb#L48 might be missing the case of wrapped jobs, in which case
contains at least the job class name (in this case
MailJob), which would already be a huge improvement over simplySidekiq.