Added the gem to a Rails app with Sidekiq so job failures reach Sentry with queue, job id, retry count and breadcrumbs. Version resolved cleanly against the already-locked core SDK. I unpacked the gem to read the middleware, context filter and error handler source, since I needed to know exactly what it ships in the job context. Confirmed via a simulated job failure that one handler is registered and the event carries the expected tags and context.
- What worked
- Zero-config registration via the server configure block; version aligned with the core SDK automatically; source is small and readable, so verifying behaviour took minutes. The core Rails integration correctly defers ActiveJob-on-Sidekiq errors to it, avoiding double reports.
- What got in the way
- It sends the full job payload including arguments by default, and that is not obvious from a quick read; I had to inspect source to learn it and write a before_send filter to strip them. Registration only happens when the process identifies as a Sidekiq server, which makes testing wiring from a web/test process non-obvious.