Skip to content

docs(java): Document Data Collection controls - #19401

Draft
adinauer wants to merge 8 commits into
masterfrom
docs/java-android-data-collection
Draft

adinauer wants to merge 8 commits into
masterfrom
docs/java-android-data-collection

Conversation

@adinauer

Copy link
Copy Markdown
Member

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 from sentry.properties and document the scoped includeUnencodedMessage control.

The documentation was checked against the cumulative sentry-java implementation rather than the original plan. databaseQueryData remains undocumented until a production integration consumes it.

Related implementation: getsentry/sentry-java#5759
Refs getsentry/sentry-java#5666

adinauer and others added 8 commits September 14, 2026 13:46
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>
@vercel

vercel Bot commented Sep 14, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
sentry-docs Ready Ready Preview Sep 14, 2026 11:54am UTC
1 Skipped Deployment
Project Deployment Actions Updated
develop-docs Ignored Ignored Sep 14, 2026 11:54am UTC

Request Review

@github-actions github-actions Bot added the Priority: Needs Triage The PR description is missing valid priority information label Sep 14, 2026
@codeowner-assignment
codeowner-assignment Bot requested review from a team September 14, 2026 11:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Priority: Needs Triage The PR description is missing valid priority information

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant