Report Active Job jobs through sentry-rails by default
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- ruby
- Domain
- backend, observability
Research direction
Read the related changes in getsentry/sentry-ruby#3130, #3134, #3145, and #3173, then locate each adapter's Railtie and its handling of Sentry::Rails.active_job_owns_adapter?. Update Sidekiq, Resque, and Delayed Job so Active Job reporting defaults to sentry-rails ownership while preserving the documented opt-out behavior. Verify the adapter and Rails integration tests cover error and span reporting; the issue identifies no test files.
Written by the indexing model from the issue text.
Description
Since 7.3.0, Sidekiq, Resque, and Delayed Job can hand their Active Job jobs to sentry-rails instead of reporting them through their own integration. This is opt-in today. In the next major, sentry-rails should own Active Job reporting for these adapters by default.
- Each adapter's Railtie adds its Active Job adapter to
config.rails.skippable_job_adapters, sosentry-railsskips those jobs unless the user removes the adapter from that list. - When
sentry-railsowns the adapter (Sentry::Rails.active_job_owns_adapter?), the adapter gem only isolates the hub and continues the trace, and leaves error and span reporting tosentry-rails. - Flipping the default changes which integration reports Active Job errors and spans for existing Sidekiq, Resque, and Delayed Job users, so it is a breaking change.
Related: getsentry/sentry-ruby#3130, getsentry/sentry-ruby#3134, getsentry/sentry-ruby#3145, getsentry/sentry-ruby#3173
Peter Solnica confirmed this was the intended direction when the opt-in landed.
via @dingsdax.
--
- Dominant language
- Ruby
- Stars
- 990
- Forks
- 553
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 31
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from getsentry/sentry-ruby
-
Bug Ruby Waiting for: Product Owner
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
getsentry/sentry-ruby#3228 · 1 comment ·
Maintainers usually reply within 1 day
-
Shorter rate limit in the same header replaces a longer onePossibly taken @sentry-junior claimed this 5 days ago. OpenBug Ruby
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
getsentry/sentry-ruby#3211 · 1 comment ·
Maintainers usually reply within 1 day
-
Events dropped client-side for size are only logged at debug level and not recorded as lostPossibly taken @sentry-junior claimed this 5 days ago. OpenBug Junior: repro Ruby
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
getsentry/sentry-ruby#3209 · 2 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
Ship fewer files with the gemsPossibly taken @solnic claimed this 1 day ago. OpenImprovement Ruby Waiting for: Product Owner
getsentry/sentry-ruby#3223 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
-
Feature Ruby Waiting for: Product Owner
Difficulty 3/5 1-2 days Newbie friendliness 54/100
getsentry/sentry-ruby#3217 · 1 comment ·
Maintainers usually reply within 1 day
All issues in getsentry/sentry-ruby
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
開発用DockerイメージにPlaywrightのシステム依存を追加するPossibly taken @momocus claimed this today. Open
Difficulty 1/5 Under an hour Newbie friendliness 85/100
sakazuki-org/sakazuki#1453 ·
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
jenkins-infra/jenkins.io#9615 · 1 comment ·
Maintainers usually reply within 1 day
-
fix(ocr): compile the Tesseract-free pipeline with Tokio runtimePossibly taken @Goldziher claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day