[adinauer]

PR Stack (Ignore HTTP Status)

• feat(tracing): Ignore incoming server HTTP statuses #6556
• feat(tracing): [Ignore HTTP Status 1] Add sentry.kind to server instrumentation #6557
• feat(core): [Ignore HTTP Status 2] Add ignoredServerHttpStatusCodesForTracing configuration #6559
• feat(tracing): [Ignore HTTP Status 3] Filter configured incoming HTTP statuses #6566
• feat(tracing): [Ignore HTTP Status 4] Ignore incoming 404s by default #6567

---

📜 Description

Default ignoredServerHttpStatusCodesForTracing to a fresh list containing HTTP 404. Completed incoming server transactions that finish with 404 are therefore no longer sent to Sentry unless users replace or clear the configuration.

Explicit custom lists still replace the default, while an empty list or empty external/Spring configuration restores tracing for every incoming HTTP status. The Spring Boot documentation and breaking-change entry include Java, properties, and YAML opt-out examples.

💡 Motivation and Context

404 transactions are commonly low-value tracing noise. This changes the default requested in #4736 while retaining the narrow filtering rules from the previous stack PR: only root server transactions with a numeric root response status are affected. Outgoing HTTP requests, errors, logs, metrics, replay, continuous profile chunks, and external OTLP export remain independent.

Fixes #4736

💚 How did you test it?

• Core SentryOptionsTest and SentryClientTest
• Spring Boot auto-configuration tests for Spring Boot 2, 3, and 4
• Servlet and WebFlux integration tests for all three Spring Boot generations
• OpenTelemetry agent and agentless integration tests for all three Spring Boot generations
• Manual Spring Boot 4 sample verification against a local envelope receiver: default 404 dropped, empty configuration retained 404, custom ranges replaced the default, and combined configurations such as 404,500-599 and 200-399,404 filtered each configured status when root response metadata was available
• make format api
• git diff --check

📝 Checklist

• I added GH Issue ID & Linear ID
• I added tests to verify the changes.
• No new PII added or SDK only sends newly added PII if sendDefaultPII is enabled.
• I updated the docs if needed.
• I updated the wizard if needed.
• Review from the native team if needed.
• No breaking change or entry added to the changelog.
• No breaking change for hybrid SDKs or communicated to hybrid SDKs.
• Public API changes reviewed by another Mobile SDK team member or implemented according to the develop docs spec.

🔮 Next steps

Coordinate the corresponding migration/options documentation in sentry-docs before the 9.x release.

⚠️ Merge this PR using a merge commit (not squash). Only the collection branch is squash-merged into main.

[github-actions]

	Messages
📖	Do not forget to update Sentry-docs with your feature once the pull request gets approved.

Generated by 🚫 dangerJS against a76505b

[sentry]

📲 Install Builds

Android

🔗 App Name	App ID	Version	Configuration
SDK Size	io.sentry.tests.size	8.63.0 (1)	release

⚙️ sentry-android Build Distribution Settings