Repository navigation
Conversation
Drop completed incoming server HTTP transactions when their root response status matches a configured range. Preserve lifecycle finalization while skipping processors, callbacks, envelope creation, and replay registration for filtered transactions. Record transaction, span, and profile losses, clean up temporary profile traces, and cover Spring Boot servlet and WebFlux integrations. Fixes #4735
Reference PR #6566 from the user-facing feature entry now that the stacked pull request has been created.
Contributor
|
📲 Install BuildsAndroid
|
7 of 9 tasks
adinauer
marked this pull request as ready for review
November 12, 2026 09:05
adinauer
requested review from
markushi and
runningcode
and removed request for
a team
November 12, 2026 09:05
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 (Ignore HTTP Status)
📜 Description
Filter completed incoming HTTP transactions in
SentryClientwhen the rootsentry.kindisserverand the numeric roothttp.response.status_codematches a configuredignoredServerHttpStatusCodesForTracingrange.The filter runs before user event processors,
beforeSendTransaction, envelope creation, transport, and replay registration. It records one discarded transaction, the root and child spans, and an attached transaction profile with theevent_processorreason. Temporary transaction-profile trace files are deleted before returning.Null or empty configuration keeps all transactions. Missing, malformed, fractional, child-only, and out-of-range status values fail open. Native
Integerand OpenTelemetryLongstatus values are supported without narrowing overflow.💡 Motivation and Context
This completes the opt-in filtering behavior for #4735 while preserving the current default: no HTTP statuses are ignored unless configured. Filtering happens only after normal transaction, performance-collector, and profiling finalization because the final HTTP response status is not known when tracing starts.
All three Spring Boot generations cover servlet and WebFlux 404 filtering. Documentation includes Java,
sentry.properties, Springapplication.properties, andapplication.ymlexamples.SDK team review found one profile client-report accounting omission; it was fixed before opening this PR.
Fixes #4735
💚 How did you test it?
./gradlew :sentry:test --tests io.sentry.SentryClientTest --tests io.sentry.SentryTracerTest --rerun-taskssentry-spring-boot,sentry-spring-boot-jakarta, andsentry-spring-boot-4make format apigit diff --check📝 Checklist
sendDefaultPIIis enabled.🔮 Next steps
The final PR defaults the option to ignoring incoming HTTP 404 transactions and documents the breaking-change migration path.