ref(logging): [Logs and Metrics Enable Flags 21] Rename Logs opt-ins

[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
• 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
• ref(logging): [Logs and Metrics Enable Flags 21] Rename Logs opt-ins #5970

---

📜 Description

Renames the generic logging-integration opt-in from enableLogs to logsEnabled before the new API is released:

• Logback XML: <logsEnabled>true</logsEnabled>
• Log4j2 plugin attribute: logsEnabled="true"
• JUL LogManager: io.sentry.jul.SentryHandler.logsEnabled=true
• Spring Boot: sentry.logging.logs-enabled=true
• Timber constructors and property: logsEnabled
• Android Timber option: timberLogsEnabled
• Android Logcat option: logcatLogsEnabled

Java integrations expose state-oriented get...Enabled() and set...Enabled() accessors, which map to natural .logsEnabled, .timberLogsEnabled, and .logcatLogsEnabled property syntax in Kotlin. Samples, tests, API dumps, and option guidance use the renamed controls.

Legacy aggregate ExternalOptions.enableLogs detection remains unchanged because it exists only to warn about obsolete logs.enabled configuration. The Android manifest keys remain io.sentry.timber.logs.enabled and io.sentry.logcat.logs.enabled.

💡 Motivation and Context

logsEnabled describes state rather than an action and provides a consistent .logsEnabled property across Kotlin-native and Java-defined integrations.

💚 How did you test it?

• ./gradlew :sentry-logback:test :sentry-log4j2:test :sentry-jul:test :sentry-android-timber:testReleaseUnitTest :sentry-android-core:testReleaseUnitTest :sentry-spring-boot:test :sentry-spring-boot-jakarta:test :sentry-spring-boot-4:test
• ./gradlew spotlessApply apiDump

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

#skip-changelog

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

[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

[runningcode]

Yes! Much better API