Repository navigation
Conversation
Contributor
Instructions and example for changelogPlease add an entry to Example: ## Unreleased
### Features
- Remove Logs and Metrics enable flags ([#5939](https://github.com/getsentry/sentry-java/pull/5939))If none of the above apply, you can opt out of this check by adding |
📲 Install BuildsAndroid
|
Require an explicit Logback appender opt-in before forwarding records as Sentry Logs. Keep event and breadcrumb capture independent while the aggregate core Logs flag remains in place. Co-Authored-By: Claude <noreply@anthropic.com>
4 of 8 tasks
Require an explicit Log4j2 appender opt-in before forwarding records as Sentry Logs. Preserve existing constructors and factory methods with Logs disabled by default while keeping events and breadcrumbs unchanged. Co-Authored-By: Claude <noreply@anthropic.com>
4 of 8 tasks
Require an explicit JUL handler opt-in before forwarding records as Sentry Logs. Support Java and LogManager configuration while keeping event and breadcrumb capture unchanged. Co-Authored-By: Claude <noreply@anthropic.com>
4 of 8 tasks
Require an explicit Timber-local opt-in before forwarding Timber messages as Sentry Logs. Add Android options and manifest configuration for auto-installed integrations while preserving event and breadcrumb capture. Co-Authored-By: Claude <noreply@anthropic.com>
4 of 8 tasks
Require an explicit Android option before forwarding Logcat calls as Sentry Logs. Support Java and manifest configuration while keeping breadcrumbs and Android Log calls unchanged. Co-Authored-By: Claude <noreply@anthropic.com>
4 of 8 tasks
Add a Spring Boot logging property that controls Sentry Logs forwarding from auto-configured Logback appenders. Keep appender installation, events, and breadcrumbs independent from the new opt-in. Co-Authored-By: Claude <noreply@anthropic.com>
Merged
4 of 8 tasks
Capture manual Sentry Logs without an aggregate enable option and always create the configured logger batch processor. Keep automatic logging integrations controlled by their local opt-ins and remove legacy Logs configuration from active samples and fixtures. Co-Authored-By: Claude <noreply@anthropic.com>
2 of 8 tasks
Detect explicit io.sentry.logs.enabled Android manifest metadata and emit tailored migration warnings without changing the integration-local Logs options. Co-Authored-By: Claude <noreply@anthropic.com>
4 of 8 tasks
Keep parsing the nullable logs.enabled external option and emit tailored migration warnings for explicit true and false values without changing manual Logs capture. Co-Authored-By: Claude <noreply@anthropic.com>
4 of 8 tasks
Inspect the Spring Environment before SDK initialization and emit tailored migration warnings for explicit sentry.logs.enabled values without binding or applying the obsolete property. Co-Authored-By: Claude <noreply@anthropic.com>
4 of 8 tasks
Replace the no-argument SentryTimberIntegration constructor with a boolean overload so manually installed integrations must choose whether to forward Sentry Logs. Keep the lazy evaluator path for auto-installed integrations and clarify the separate Android option and constructor configuration paths. BREAKING CHANGE: SentryTimberIntegration() now requires a logsEnabled argument. Co-Authored-By: Claude <noreply@anthropic.com>
feat(logback): [Logs and Metrics Enable Flags 1] Add Logs opt-in
feat(log4j2): [Logs and Metrics Enable Flags 2] Add Logs opt-in
feat(jul): [Logs and Metrics Enable Flags 3] Add Logs opt-in
feat(android): [Logs and Metrics Enable Flags 4] Add Timber Logs opt-in
feat(android): [Logs and Metrics Enable Flags 5] Add Logcat Logs opt-in
feat(spring): [Logs and Metrics Enable Flags 6] Add logging Logs opt-in for Spring Boot
Remove the internal no-op batch processor now that SentryClient always creates the configured Logs processor and no SDK path selects the stub. Co-Authored-By: Claude <noreply@anthropic.com>
Propagate removal of the unused no-op Logs batch processor through the stack while preserving branch ancestry.
Propagate the updated Logs enable-flag removal through the stack while preserving branch ancestry.
Remove the internal no-op batch processor now that SentryClient always creates the configured Metrics processor and no SDK path selects the stub. Co-Authored-By: Claude <noreply@anthropic.com>
Propagate removal of unused no-op telemetry batch processors through the stack while preserving branch ancestry.
Propagate removal of unused no-op telemetry batch processors through the stack while preserving branch ancestry.
Propagate removal of unused no-op telemetry batch processors through the stack while preserving branch ancestry.
Propagate removal of unused no-op telemetry batch processors through the stack while preserving branch ancestry.
Propagate removal of unused no-op telemetry batch processors through the stack while preserving branch ancestry.
feat(core): [Logs and Metrics Enable Flags 7] Remove Logs enable flag
perf(core): [Logs and Metrics Enable Flags 8] Avoid unused Logs worker thread
feat(core): [Logs and Metrics Enable Flags 9] Remove Metrics enable flag
…st-use perf(core): [Logs and Metrics Enable Flags 10] Avoid unused Metrics worker thread
fix(jul): [Logs and Metrics Enable Flags 11] Preserve null-message records
docs: [Logs and Metrics Enable Flags 12] Update options guidance
fix(android): [Logs and Metrics Enable Flags 13] Read Timber option lazily
Remove the constructor superseded by the minimumLevel overload in 8.16.0 at the v9 breaking-change boundary. Co-Authored-By: Claude <noreply@anthropic.com>
Rename the Timber and Logcat manifest options to describe Sentry's log capture direction consistently with their Android option accessors. Co-Authored-By: Claude <noreply@anthropic.com>
ref(logging): [Logs and Metrics Enable Flags 14] Rename Logs opt-ins
Resolve conflicts while preserving source-local Logs controls and the removal of aggregate Logs and Metrics flags. Co-Authored-By: Claude <noreply@anthropic.com>
List the exact option, property, attribute, and manifest names for every logging integration so users can enable the intended source after upgrading. Co-Authored-By: Claude <noreply@anthropic.com>
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
PR Stack (Logs and Metrics Enable Flags)
📜 Description
Collection PR for the Logs and Metrics enable-flag removal stack. Squash-merge this once all stack PRs are merged.
💡 Motivation and Context
Removes the aggregate Logs and Metrics enable flags, adds integration-local Logs opt-ins, and avoids starting unused batch worker threads.
💚 How did you test it?
Each PR in the stack includes focused tests. The completed stack will run the full repository checks and aggregate Javadocs.
📝 Checklist
sendDefaultPIIis enabled.🔮 Next steps
Merge each stack PR into this collection branch in order using merge commits, then squash-merge this PR into
9.x.x.