Conversation
Add an internal marker to SDK event processors across core and integrations. Keep customer processors and the backfilling marker independent so later callback handling can distinguish ownership regardless of registration path. Leave exception handling unchanged in this preparatory change. Refs #6081 Co-Authored-By: Claude <noreply@anthropic.com>
This was referenced Sep 24, 2026
📲 Install BuildsAndroid
|
This was referenced Sep 24, 2026
This branch has not been deployed
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.
PR Stack (Callback Errors)
📜 Description
Adds the internal
SentryEventProcessormarker and applies it to all 25 SDK-owned event processor implementations across core, Android, Servlet, Spring, and OpenTelemetry. Customer processors continue implementingEventProcessor;BackfillingEventProcessorremains independent.This is preparatory only: exception handling and event delivery behavior are unchanged.
💡 Motivation and Context
SDK integrations register processors through the same options and scope APIs as customers, so registration location cannot identify ownership. The marker lets #6142 distinguish SDK processors from customer processors when its failure policy is updated later, without adding a method to the customer-facing interface.
Refs #6081.
💚 How did you test it?
./gradlew spotlessApply apiDump./gradlew :sentry:test --tests='*SentryEventProcessorTest*' apiCheck --info📝 Checklist
sendDefaultPIIis enabled.🔮 Next steps
Update #6142 to apply customer-callback failure handling only to unmarked processors. Customer subclasses of SDK processors inherit the marker; this marker identifies the SDK class hierarchy, not arbitrary overridden method ownership.
#skip-changelog