Repository navigation
Conversation
solnic
marked this pull request as draft
October 13, 2026 13:25
solnic
force-pushed
the
feat/3117-public-backend-extension-registry-for-background-job-integrations
branch
from
October 14, 2026 09:17
120f7a3 to
24621bb
Compare
solnic
marked this pull request as ready for review
October 14, 2026 09:49
solnic
force-pushed
the
feat/3117-public-backend-extension-registry-for-background-job-integrations
branch
3 times, most recently
from
October 14, 2026 11:42
18edb4c to
605bebc
Compare
solnic
marked this pull request as draft
October 15, 2026 08:25
solnic
force-pushed
the
feat/3117-public-backend-extension-registry-for-background-job-integrations
branch
3 times, most recently
from
October 15, 2026 11:00
2cddb72 to
3fa983c
Compare
solnic
marked this pull request as ready for review
October 15, 2026 12:19
solnic
force-pushed
the
feat/3117-public-backend-extension-registry-for-background-job-integrations
branch
2 times, most recently
from
October 15, 2026 12:51
27970e7 to
e3ade51
Compare
solnic
force-pushed
the
feat/3117-public-backend-extension-registry-for-background-job-integrations
branch
from
October 15, 2026 13:37
5eaa1a5 to
77e02b1
Compare
solnic
force-pushed
the
feat/3117-public-backend-extension-registry-for-background-job-integrations
branch
3 times, most recently
from
October 23, 2026 11:49
35fb71a to
0df0bb8
Compare
This was referenced Nov 2, 2026
solnic
force-pushed
the
feat/3117-public-backend-extension-registry-for-background-job-integrations
branch
from
November 2, 2026 15:56
0df0bb8 to
f5eee4a
Compare
solnic
marked this pull request as draft
November 2, 2026 15:57
solnic
force-pushed
the
feat/3117-public-backend-extension-registry-for-background-job-integrations
branch
3 times, most recently
from
November 3, 2026 12:01
a213bfd to
7e7b39b
Compare
solnic
marked this pull request as ready for review
November 3, 2026 14:29
solnic
force-pushed
the
feat/3117-public-backend-extension-registry-for-background-job-integrations
branch
2 times, most recently
from
November 4, 2026 10:25
8c54390 to
f9f7593
Compare
solnic
force-pushed
the
feat/3117-public-backend-extension-registry-for-background-job-integrations
branch
2 times, most recently
from
November 4, 2026 15:02
bf6aff9 to
6a05c59
Compare
solnic
force-pushed
the
feat/3117-public-backend-extension-registry-for-background-job-integrations
branch
from
November 5, 2026 09:50
6a05c59 to
5b2d854
Compare
sl0thentr0py
requested changes
Nov 5, 2026
Member
|
approving to unblock, feel free to address comments or not |
sl0thentr0py
approved these changes
Nov 5, 2026
solnic
force-pushed
the
feat/3117-public-backend-extension-registry-for-background-job-integrations
branch
2 times, most recently
from
November 9, 2026 09:54
cf33189 to
f5e2c72
Compare
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Want reviews to match your repository better? Bugbot Learning can learn team-specific rules from PR activity. A team admin can enable Learning in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit f5e2c72. Configure here.
solnic
force-pushed
the
feat/3117-public-backend-extension-registry-for-background-job-integrations
branch
from
November 10, 2026 13:45
f5e2c72 to
a6b58ce
Compare
Document and name the caller > scope > extension merge in merged_error_data, and skip capture when the SDK is not initialized.
hook_hash only coerces the top-level value scope_data returns, and apply_scope_data ran outside safely. A tags, extra, user or context value that is not a Hash made the Scope setters raise ArgumentError from start_job, so the job never ran. Apply the scope data through safely, as the other hooks are, so the failure is logged and the job runs.
solnic
force-pushed
the
feat/3117-public-backend-extension-registry-for-background-job-integrations
branch
from
November 10, 2026 19:27
0e122f4 to
2b10566
Compare
solnic
deleted the
feat/3117-public-backend-extension-registry-for-background-job-integrations
branch
November 11, 2026 09:02
3 tasks done
dingsdax
added a commit
to getsentry/sentry-changelog
that referenced
this pull request
Nov 18, 2026
Adds a changelog post for [sentry-ruby 7.3.0](https://github.com/getsentry/sentry-ruby/releases/tag/7.3.0), so Ruby users hear about the release's new features in the changelog and in Sentry's "What's New" panel (scoped to Ruby, Rails, and Rack orgs) and not only in the GitHub release notes. The post is framed around background work that fails quietly, and each section leads with the problem it solves: - **Know when a GoodJob cron job fails or never runs**: `config.enabled_patches << :good_job_cron` puts every GoodJob cron entry under Crons monitoring (getsentry/sentry-ruby#3200) - **See which feature flags were on when an error happened**: `Sentry.add_feature_flag` attaches flag evaluations to errors and spans (getsentry/sentry-ruby#3108) - **Spot jobs piling up in the queue**: ActiveJob, Sidekiq, and Resque jobs report queue wait time and payload size for the Queues dashboard (getsentry/sentry-ruby#3133) It closes with `Sentry.logger` block support (getsentry/sentry-ruby#3178), then links the full release notes. The new job extensions API (getsentry/sentry-ruby#3129) is left out because it only matters to people who maintain job backends. Nothing breaks. Open decisions: - The entry is `published: false`, so merging only creates it. To go live, set `published: true` before merge or publish it from the admin UI. - `author` is left unset because I couldn't confirm which email belongs to an existing changelog user. Add one if you want the post attributed. <!-- junior-request-attribution:start --> via @dingsdax. <!-- junior-request-attribution:end --> <!-- junior-session-footer:start --> <!-- junior-conversation-id:local%3Aweb%3Ab5614f77a180622dc700158a --> -- [View Session](https://junior-prod.sentry.dev/conversations/local%3Aweb%3Ab5614f77a180622dc700158a) [[Sentry]](https://sentry.sentry.io/explore/conversations/local%3Aweb%3Ab5614f77a180622dc700158a/?project=4510944073809921) <!-- junior-session-footer:end --> --------- Co-authored-by: sentry-junior[bot] <264270552+sentry-junior[bot]@users.noreply.github.com> Co-authored-by: johdax <114897+dingsdax@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

This introduces a public API for queue systems (ActiveJob, Sidekiq, GoodJob, SolidQueue etc.) to integrate with Sentry by subclassing
Sentry::JobExtensions::Extension:Integrations call the extension around enqueueing and performing a job:
These record the
queue.publishspan and thequeue.processtransaction, and capture the job's exceptions. The data they record comes from hooks the subclass overrides, such asscope_data,error_data,messaging_data,will_retry?,report_exception?,record_publish_span?,extract_trace_headers,inject_trace_headers,transaction_nameandspan_origin.Hooks take keyword arguments and accept keywords they don't read, so integrations can pass extra context. A failing hook is logged and the job runs without its data.
Closes #3117
Closes #3123