PR Stack (Data Collection)

• feat(core): Data Collection #5759
• feat(core): [Data Collection 1] Add configuration types #5760
• feat(core): [Data Collection 2] Expose SentryOptions API #5761
• feat(core): [Data Collection 3] Add policy resolver #5799
• feat(graphql): [Data Collection 4] Apply GraphQL policies #5800
• feat(database): [Data Collection 5] Apply query policy #5801
• feat(spring): [Data Collection 6] Apply incoming request body policy #5802
• feat(apollo): [Data Collection 7] Apply incoming response body policy #5803
• feat(apollo): [Data Collection 8] Apply outgoing request body policy #5804
• feat(graphql): [Data Collection 9] Apply outgoing response body policy #5805
• feat(http): [Data Collection 10] Apply request header policy #5806
• feat(http): [Data Collection 11] Apply response header policy #5807
• feat(http): [Data Collection 12] Apply query parameter policy #5810
• feat(http): [Data Collection 13] Apply cookie collection policy #5811
• feat(user): [Data Collection 14] Apply user information policy #5812
• fix(android): [Data Collection 15] Scope device info cache to SDK options #5831
• test(replay): [Data Collection 16] Keep Replay independent #5832
• fix(spring): [Data Collection 18] Bind key-value policies #5834
• fix(android): [Data Collection 19] Preserve installation ID #5937
• fix(ktor): [Data Collection 20] Exclude query parameters from span descriptions #5983
• feat(core): [Data Collection 21] Add external configuration #6036
• feat(android): [Data Collection 22] Add manifest configuration #6038
• fix(core): [Data Collection 23] Support WebSocket URL parsing #6064
• fix(core): [Data Collection 24] Narrow utility exception handling #6065
• feat(core): [Data Collection 25] Apply file path policy #6075
• feat(logback): [Data Collection 26] Add unencoded message opt-in #6076
• fix(core): [Data Collection 27] Make opt-in explicit #6122

📜 Description

Add includeUnencodedMessage to the Logback SentryAppender. When an encoder is configured, this explicit integration option includes the original message template and parameters alongside the encoded output.

Keep sendDefaultPii=true as a temporary compatibility opt-in, including when Data Collection is configured. Without an encoder, the appender preserves its existing behavior and includes the original message data.

💡 Motivation and Context

Logback encoders can mask or remove PII before Sentry receives the formatted message. The existing guard relies only on the broad legacy sendDefaultPii option. This adds a narrow Logback-specific opt-in without introducing a Data Collection category for raw log messages.

Refs #5666

💚 How did you test it?

• ./gradlew :sentry-logback:check
• ./gradlew spotlessApply apiDump
• .venv/bin/python test/system-test-runner.py test --module sentry-samples-logback --agent false --auto-init true --build true
• One-off Logback system test with a regex-masking encoder and includeUnencodedMessage=true, verifying encoded bodies and original event/log template parameters
• 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

Merge this PR into the previous stack branch before merging the remaining Data Collection stack into the collection branch.

#skip-changelog

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