Problem Statement

Our app includes both sentry-rails and sentry-sidekiq, and we moved a lot of our codebase to use the Rails.error API.

We use Rails.error.set_context on a few places on our app (instead of Sentry.with_scope) to enrich reports with extra info, but when the exception is raised inside a background job it isn't included on the issue.

Would make sense to have some integration between those two gems to make Sentry::Sidekiq.capture_exception go through the Rails reporter instead of its default implementation?

Solution Brainstorm

No response