Repository navigation
docs(java): Update Logs and Metrics configuration for v9 - #19962
Merged
Merged
Conversation
Remove the obsolete global Logs and Metrics enable options from Java and Android documentation. Document integration-specific automatic log capture flags and add migration guidance for the v9 breaking changes. Co-Authored-By: Claude <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
github-actions
Bot
added
the
Priority: Needs Triage
dingsdax
added a commit
that referenced
this pull request
Oct 15, 2026
…8.59.0 (#19995) Since Java/Android SDK 8.59.0 ([getsentry/sentry-java#6184](getsentry/sentry-java#6184)), direct `Sentry.logger()` and `Sentry.metrics()` calls are captured regardless of `logs.enabled` / `metrics.enabled`. `logs.enabled` now only gates automatic logging integrations, and `metrics.enabled` has no effect. The Java and Android Logs setup pages still say `logs.enabled` is required to enable logging, and the Metrics options pages (Java, Spring Boot, Android) still say `metrics.enabled=false` disables metrics entirely. This adjusts those sentences in place, keeping the existing structure and examples for older SDK versions. The flags are removed entirely in v9; that guidance is handled separately in #19962. Refs SDK-1533 <!-- junior-request-attribution:start --> via **johdax**. <!-- junior-request-attribution:end --> <!-- junior-session-footer:start --> <!-- junior-conversation-id:slack%3AD0ANK27LVV0%3A1792069918.618529 --> -- [View Junior Session](https://junior-prod.sentry.dev/conversations/slack%3AD0ANK27LVV0%3A1792069918.618529) [[Sentry]](https://sentry.sentry.io/explore/conversations/slack%3AD0ANK27LVV0%3A1792069918.618529/?project=4510944073809921) <!-- junior-session-footer:end --> Co-authored-by: sentry-junior[bot] <264270552+sentry-junior[bot]@users.noreply.github.com> Co-authored-by: Johannes Daxboeck <johannes.daxboeck@sentry.io>
1 of 6 tasks
markushi
approved these changes
Oct 29, 2026
| } | ||
| ``` | ||
|
|
||
| The Android Gradle plugin's `logcat.enabled` option controls Logcat bytecode instrumentation. `logcatLogCaptureEnabled` controls whether the instrumented records are also sent as Sentry Logs. |
Co-authored-by: Markus Hintersteiner <markus.hintersteiner@sentry.io>
adinauer
marked this pull request as ready for review
October 29, 2026 10:13
Contributor
|
Please update the IS YOUR CHANGE URGENT? section of the PR description:
This information helps the Docs team prioritize your review. |
Contributor
|
Services awaiting deployment · Rollout details
Mention |
This branch was successfully 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
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.
Update the Java and Android Logs and Metrics documentation for the v9 behavior introduced by sentry-java#5939.
Manual
Sentry.logger()andSentry.metrics()calls no longer require global enable flags. Automatic Logback, Log4j 2, JUL, Spring Boot, Timber, and Logcat capture now documents the corresponding integration-specific opt-in. This also adds Java and Android migration guidance for removed configuration surfaces and constructor changes.This PR targets the
java-v9collection branch instead ofmasterso these changes can land with the other Java v9 documentation and become active together when v9 is released.