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 for Spring Boot #5946
• feat(core): [Logs and Metrics Enable Flags 7] Remove Logs enable flag #5947
• perf(core): [Logs and Metrics Enable Flags 8] Avoid unused Logs worker thread #5952
• feat(core): [Logs and Metrics Enable Flags 9] Remove Metrics enable flag #5953
• perf(core): [Logs and Metrics Enable Flags 10] Avoid unused Metrics worker thread #5957
• fix(jul): [Logs and Metrics Enable Flags 11] Preserve null-message records #5960
• docs: [Logs and Metrics Enable Flags 12] Update options guidance #5961
• fix(android): [Logs and Metrics Enable Flags 13] Read Timber option lazily #5964
• ref(logging): [Logs and Metrics Enable Flags 14] Rename Logs opt-ins #5970

---

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

Removes the legacy external and Android manifest Logs configuration, along with active legacy Logs configuration in 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

Avoid starting the Logs batch worker thread until it is first needed.

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

[github-actions]

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

Generated by 🚫 dangerJS against 67e11cc

[sentry]

📲 Install Builds

Android

🔗 App Name	App ID	Version	Configuration
SDK Size	io.sentry.tests.size	8.58.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

[lbloder]

LGTM 👍

[lbloder]

Do we still need NoOpLoggerBatchProcessor?

[adinauer]

Removed NoOpLoggerBatchProcessor in 67e11cc. It had no remaining SDK call sites after removing the aggregate Logs enable flag; supported suppression remains available through beforeSendLog.