Implement Sentry’s Celery integration in SDK #57800
Merged
Conversation
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
uranusjr
requested review from
XD-DENG,
amoghrajesh,
ashb,
hussein-awala,
jedcunningham,
kaxil,
o-nikolas and
pierrejeambrun
as code owners
boring-cyborg
bot
added
area:Executors-core
uranusjr
force-pushed
the
sentry-in-sdk-celery-support
branch
from
bc076aa to
b4ce178
Compare
uranusjr
force-pushed
the
sentry-in-sdk-celery-support
branch
11 times, most recently
from
47612d8 to
6976e7e
Compare
ephraimbuddy
approved these changes
Nov 17, 2025
uranusjr
force-pushed
the
sentry-in-sdk-celery-support
branch
from
6976e7e to
82bbb6a
Compare
itayweb
pushed a commit
to itayweb/airflow
that referenced
this pull request
Dec 6, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Follow-up to #57032.
An executor should declare the integration it wants to support. That declaration (an import path) is sent to a task when the executor runs it as a part of the workload. The SDK loads that string to RuntimeTaskInstance, and the Sentry integration code uses it to import the relevant callable to run.
Since the integration information is only known when the executor passes it to the task runner, I changed the Sentry integration to be initialised lazily when
enrich_erroris called (instead of__init__i.e. initialised when the task runner process starts).