feat(spring): [Logs and Metrics Enable Flags 10] Warn for legacy Logs property

[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

Injects the Spring Environment into SDK initialization for all three Spring Boot variants and detects explicit sentry.logs.enabled configuration. Migration warnings are emitted after Sentry.init, when the diagnostic logger has been initialized.

Both true and false values emit tailored migration warnings. The obsolete property is not restored to SentryProperties and does not affect capture or the new sentry.logging.enable-logs integration control. Absent configuration emits no warning.

💡 Motivation and Context

After removal of the aggregate Logs option, Spring's relaxed binder ignores the old property. Inspecting the complete Spring Environment preserves a useful migration diagnostic across property files, YAML, environment variables, command-line values, and other property sources.

💚 How did you test it?

• ./gradlew :sentry-spring-boot:test :sentry-spring-boot-jakarta:test :sentry-spring-boot-4:test
• ./gradlew spotlessApply apiDump
• Added absent, explicit true, and explicit false tests to all three Spring Boot variants
• Verified the integration-local Logback Logs opt-in remains disabled

📝 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 the first accepted Log item.

#skip-changelog

⚠️ 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 8c2f35f

[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	340.88 ms	401.77 ms	60.89 ms
Size	0 B	0 B	0 B

Baseline results on branch: feat/warn-legacy-logs-external

Startup times

Revision	Plain	With Sentry	Diff
623c4e5	312.67 ms	343.90 ms	31.23 ms

App size

Revision	Plain	With Sentry	Diff
623c4e5	0 B	0 B	0 B

Previous results on branch: feat/warn-legacy-logs-spring

Startup times

Revision	Plain	With Sentry	Diff
c2e4325	310.06 ms	363.22 ms	53.16 ms

App size

Revision	Plain	With Sentry	Diff
c2e4325	0 B	0 B	0 B

[sentry]

Bug: The application will crash on startup if sentry.logs.enabled is set to a non-boolean value, as the call to environment.getProperty lacks error handling for invalid conversions.
_{Severity: HIGH}

Suggested Fix

Wrap the environment.getProperty("sentry.logs.enabled", Boolean.class) call in a try-catch block to handle ConversionFailedException. Log a warning if the property value is invalid and default to a sensible value (e.g., false) to allow the application to start successfully. This makes the configuration more robust against user error.

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-spring-boot-jakarta/src/main/java/io/sentry/spring/boot/jakarta/SentryAutoConfiguration.java#L200-L201

Potential issue: The code checks for the existence of the `sentry.logs.enabled` property
but does not validate its value before attempting to convert it to a `Boolean`. If a
user provides a non-boolean string (e.g., "enabled" instead of "true"), Spring's
`StringToBooleanConverter` will throw a `ConversionFailedException`. Since this
exception is not caught during the creation of the `sentryHub` bean, it will propagate
up and cause the entire Spring application context to fail to initialize, preventing the
application from starting.

Also affects:

• sentry-spring-boot/src/main/java/io/sentry/spring/boot/SentryAutoConfiguration.java:195~196
• sentry-spring-boot-4/src/main/java/io/sentry/spring/boot4/SentryAutoConfiguration.java:198~199

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