Conversation
Replace sendDefaultPii guidance with granular Data Collection options across Java and Android documentation. Document defaults, migration behavior, integration coverage, and onboarding configuration. Co-Authored-By: Claude <noreply@anthropic.com>
Document the default-enabled filePaths control across Java and Android configuration surfaces. Correct migration and File I/O guidance so it matches the cumulative SDK implementation. Prefer Logback's scoped includeUnencodedMessage option instead of retaining the broad legacy PII switch. Co-Authored-By: Claude <noreply@anthropic.com>
Remove databaseQueryData from the Java and Android documentation while no production integration consumes it. Document the option when an integration can provide concrete configuration behavior. Co-Authored-By: Claude <noreply@anthropic.com>
Preserve the existing sendDefaultPii descriptions while marking the option as legacy. Align the Data Collected pages with current defaults and filtering behavior. Co-Authored-By: Claude <noreply@anthropic.com>
Restore pre-existing formatting changed during the Data Collection update. Keep quote, wrapping, XML, and snippet changes out of the branch diff. Co-Authored-By: Claude <noreply@anthropic.com>
Add comments after userInfo examples in Java setup snippets. Make it clear that developers can configure other collection categories. Co-Authored-By: Claude <noreply@anthropic.com>
Set Data Collection availability to 8.57.0 and clarify that enabling it ignores the legacy sendDefaultPii option. Co-Authored-By: Claude <noreply@anthropic.com>
Explain how key-value collection behavior maps to code and external settings. Link header controls to option details and limit Spring Boot properties to its guide. Co-Authored-By: Claude <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
github-actions
Bot
added
the
Priority: Needs Triage
lbloder
reviewed
Sep 15, 2026
| <meta-data | ||
| android:name="io.sentry.data-collection.user-info" | ||
| android:value="false" /> | ||
| <meta-data |
Collaborator
There was a problem hiding this comment.
does the incoming_request make sense here? Android should only have outgoing, correct?
| | Field | Type | Default | Behavior | | ||
| | ------------------------ | ---------------------------- | -------------- | ----------------------------------------------------------------------------------------------------------------------------------------- | | ||
| | `userInfo` | `boolean` | `true` | Allows integrations to populate user identity and IP address information. | | ||
| | `cookies`\* | `KeyValueCollectionBehavior` | `DENY_LIST` | Collects cookies and filters sensitive values. | |
Collaborator
There was a problem hiding this comment.
KeyValueCollectionBehavior API is not listed/explained. Should there be a separate section to explain the usage and meaning of off(), allowList(...), denyList(...), setMode(), and setTerms?
lbloder
reviewed
Sep 15, 2026
Use the client-side request and response directions supported by Android integrations in the manifest example. Co-Authored-By: Claude <noreply@anthropic.com>
Document the complete built-in key-name term list so customers know which cookie, header, and query parameter values are filtered by default. Co-Authored-By: Claude <noreply@anthropic.com>
Warn that Data Collection does not automatically cover every header omitted by legacy filtering and document the extended identifying-data deny terms. Co-Authored-By: Claude <noreply@anthropic.com>
Show the public factory method for each key-value collection mode so users can translate the documented behavior directly into Java or Kotlin code. Co-Authored-By: Claude <noreply@anthropic.com>
Remove Java-style semicolons from the Kotlin initialization example and restore Prettier formatting in the manual setup page. Co-Authored-By: Claude <noreply@anthropic.com>
Explain that general HTTP header controls do not expose cookie values and point readers to the separate cookie Data Collection setting. Co-Authored-By: Claude <noreply@anthropic.com>
Distinguish sensitive header handling from URL and query string collection when OpenTelemetry attributes are mapped to Sentry requests. Co-Authored-By: Claude <noreply@anthropic.com>
Update the Kotlin manual setup example to modify the Data Collection object loaded from manifest metadata instead of replacing it. Co-Authored-By: Claude <noreply@anthropic.com>
Update the Java manual setup example to modify the Data Collection object loaded from manifest metadata instead of replacing it. Co-Authored-By: Claude <noreply@anthropic.com>
Identify the callbacks used to filter breadcrumbs, events, and Sentry Logs when Data Collection does not control their content. Co-Authored-By: Claude <noreply@anthropic.com>
Identify the callbacks used to filter breadcrumbs, events, and Sentry Logs when Data Collection does not control their content. Co-Authored-By: Claude <noreply@anthropic.com>
Stop claiming that Data Collection controls database query data because no Android integration currently applies that option. Co-Authored-By: Claude <noreply@anthropic.com>
Stop claiming that Data Collection controls database query data because no Java integration currently applies that option. Co-Authored-By: Claude <noreply@anthropic.com>
Point Data Collection property users to the external configuration setup required for plain Java applications. Co-Authored-By: Claude <noreply@anthropic.com>
List the integrations that collect body content and distinguish content controls from body-size metadata. Co-Authored-By: Claude <noreply@anthropic.com>
Explain how Spring and Spring Boot apply both Data Collection body directions and maxRequestBodySize without implying that the limit affects other bodies. Co-Authored-By: Claude <noreply@anthropic.com>
Replace constructor-based Data Collection setup with forceDataCollection() and update migration guidance for the explicit opt-in API. Co-Authored-By: Claude <noreply@anthropic.com>
Mark Data Collection as available in 8.58.0 for Java and Android. Co-Authored-By: Claude <noreply@anthropic.com>
lbloder
reviewed
Sep 18, 2026
Explain that Data Collection sends HTTP headers when migrating from sendDefaultPii=false. Co-Authored-By: Claude <noreply@anthropic.com>
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
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.
Document the Java and Android Data Collection controls planned for SDK 8.57.0.
This explains the new defaults, migration behavior from
sendDefaultPii, built-in filtering, and configuration through code, properties, environment variables, Spring Boot, and Android manifest metadata. It also documents support across HTTP, GraphQL, Apollo, OkHttp, Ktor, OpenFeign, and File I/O integrations.Update onboarding examples to opt into Data Collection with
userInfo=false, matching the privacy-conscious JavaScript setup without adding unnecessary body configuration. Update Logback setup to load SDK options fromsentry.propertiesand document the scopedincludeUnencodedMessagecontrol.The documentation was checked against the cumulative sentry-java implementation rather than the original plan.
databaseQueryDataremains undocumented until a production integration consumes it.Related implementation: getsentry/sentry-java#5759
Refs getsentry/sentry-java#5666