// the find
getsentry/sentry-java
A Sentry SDK for Java, Android and other JVM languages.
The official Sentry SDK for Java, Android, and other JVM languages. Handles error reporting, performance monitoring, session replay, and profiling across a wide surface area: Spring Boot, Ktor, OkHttp, Apollo, Kafka, GraphQL, Logback, Log4j2, and more. If you're running JVM services or Android apps and need crash/error observability, this is the SDK you'd actually use.
The integration breadth is real — separate modules for Spring Boot 2/3/4, both javax and jakarta servlet APIs, and Apollo 3/4 means you're not stuck shimming things yourself. The Android-specific work is substantial: NDK crash capture, tombstone parsing, session replay with a pixel-level screen recorder, frame metrics tied to spans, and ANR detection that goes beyond the watchdog pattern. The BOM package (`sentry-bom`) lets you lock all module versions in one place, which matters in a monorepo. The release lifecycle (pre-release → latest → stable with explicit promotion criteria) is more disciplined than most SDK projects.
The module count is unwieldy — 50+ artifacts means picking the right combination is non-obvious, and the README doesn't help you figure out what to actually add for a standard Spring Boot app. Self-hosted Sentry users hit version compatibility walls that aren't surfaced at init time, just discovered when events stop ingesting. The OpenTelemetry integration exists but the relationship between Sentry spans and OTEL traces is murky; the docs don't clearly explain what you lose if you're already running an OTEL collector. Android session replay requires API 26+ while the rest of the Android SDK targets API 21, so you'll silently get no replay on a meaningful chunk of devices without realizing it.