feat(core): [Logs and Metrics Enable Flags 7] Remove Logs enable flag

[adinauer]

PR Stack (Logs and Metrics Enable Flags)

• feat(core): Remove Logs and Metrics enable flags #5939
• feat(logback): [Logs and Metrics Enable Flags 1] Add Logs opt-in #5940
• feat(log4j2): [Logs and Metrics Enable Flags 2] Add Logs opt-in #5941
• feat(jul): [Logs and Metrics Enable Flags 3] Add Logs opt-in #5942
• feat(android): [Logs and Metrics Enable Flags 4] Add Timber Logs opt-in #5943
• feat(android): [Logs and Metrics Enable Flags 5] Add Logcat Logs opt-in #5945
• feat(spring): [Logs and Metrics Enable Flags 6] Add logging Logs opt-in #5946
• feat(core): [Logs and Metrics Enable Flags 7] Remove Logs enable flag #5947
• feat(android): [Logs and Metrics Enable Flags 8] Warn for legacy Logs metadata #5949
• feat(core): [Logs and Metrics Enable Flags 9] Warn for legacy Logs configuration #5950
• feat(spring): [Logs and Metrics Enable Flags 10] Warn for legacy Logs property #5951
• perf(core): [Logs and Metrics Enable Flags 11] Avoid unused Logs worker thread #5952
• feat(core): [Logs and Metrics Enable Flags 12] Remove Metrics enable flag #5953
• feat(android): [Logs and Metrics Enable Flags 13] Warn for legacy Metrics metadata #5954
• feat(core): [Logs and Metrics Enable Flags 14] Warn for legacy Metrics configuration #5955
• feat(spring): [Logs and Metrics Enable Flags 15] Warn for legacy Metrics property #5956
• perf(core): [Logs and Metrics Enable Flags 16] Avoid unused Metrics worker thread #5957
• fix(jul): [Logs and Metrics Enable Flags 17] Preserve null-message records #5960
• docs: [Logs and Metrics Enable Flags 18] Update options guidance #5961
• fix(android): [Logs and Metrics Enable Flags 19] Read Timber option lazily #5964
• fix(core): [Logs and Metrics Enable Flags 20] Make migration warnings visible #5966

---

📜 Description

Removes SentryOptions.Logs.isEnabled and setEnabled and the aggregate Logs gate from LoggerApi. Manual Sentry.logger() calls now capture Logs whenever the SDK is enabled.

SentryClient now always creates the configured logger batch processor. Logback, Log4j2, JUL, Timber, and Logcat continue to require their integration-local opt-ins introduced earlier in this stack.

Stops applying the legacy external and Android manifest values while retaining their parsing/accessors and metadata key for migration warnings in the following PRs. Removes active legacy Logs configuration from samples and test fixtures.

💡 Motivation and Context

The aggregate Logs flag duplicates integration-local controls and makes manual structured logging require an unnecessary global opt-in. Removing it gives Sentry.logger() the same direct capture semantics as other SDK APIs while local integration flags prevent unexpected automatic log forwarding.

💚 How did you test it?

• ./gradlew spotlessApply apiDump
• ./gradlew :sentry:test :sentry-android-core:testReleaseUnitTest
• ./gradlew :sentry-logback:test :sentry-log4j2:test :sentry-jul:test :sentry-android-timber:testReleaseUnitTest
• ./gradlew :sentry-spring-boot:test :sentry-spring-boot-jakarta:test :sentry-spring-boot-4:test
• Updated core and integration tests to verify capture without the aggregate option and continued local gating

📝 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.

🔮 Next steps

Add targeted warnings for legacy Android manifest, external, and Spring Boot Logs configuration.

⚠️ 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 b9d76ce

[sentry]

📲 Install Builds

Android

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

⚙️ sentry-android Build Distribution Settings

[github-actions]

Performance metrics 🚀

	Plain	With Sentry	Diff
Startup time	318.02 ms	383.41 ms	65.39 ms
Size	0 B	0 B	0 B

[sentry]

Bug: The logs.enabled configuration is now parsed but silently ignored, causing logs to be captured even when users have explicitly disabled them.
_{Severity: MEDIUM}

Suggested Fix

To prevent this silent breaking change, either restore the functionality of the logs.enabled flag or add a prominent warning when this deprecated configuration is detected. This will inform users about the change in behavior and guide them on how to properly configure logging going forward, preventing unexpected data capture.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent. Verify if this is a real issue. If it is, propose a fix; if not, explain why it's
not valid.

Location: sentry/src/main/java/io/sentry/SentryOptions.java#L3733-L3738

Potential issue: The `logs.enabled` configuration property is now parsed but silently
ignored. The pull request removes the `enable` field from `SentryOptions.Logs` and the
corresponding `options.getLogs().isEnabled()` checks in `SentryClient` and
`LoggerApi.captureLog()`. As a result, users who have explicitly set
`logs.enabled=false` in their configuration to disable logging will find that logs are
now captured and sent as long as the SDK itself is enabled. This silent breaking change
goes against explicit user configuration and can lead to unexpected data collection and
network usage.

Also affects:

• sentry-android-core/src/main/java/io/sentry/android/core/ManifestMetadataReader.java:706~711

_{Did we get this right? 👍 / 👎 to inform future reviews.}