Fresh install
Never used Sentry? Start here.
- 1. Compose up on your host
- 2. Install sentry-java
- 3. Init with the Epure DSN and verify
JavaError tracking for Java with sentry-java
Use this page for the JVM SDK: Quarkus, Micronaut, and servlets. Spring Boot is /integrations/spring-boot. Android is out of scope. Add io.sentry:sentry via Maven or Gradle and set the DSN to your Epure host. Exceptions land as issues grouped on raw frames.
Host up → install SDK → paste DSN → confirm a 202.
Start here
From zero, or from Sentry.
Same finish line: sentry-java pointing at your Epure DSN, first issue in the list.
Already on Sentry
Keep the SDK. Change the DSN.
- 1. Create an Epure project and copy the DSN
- 2. Replace only the dsn string in init
- 3. Set traces/replay/profile rates to 0
Docs for this stack
The fit
Epure is the error tracker for Java.
Install sentry-java once. Point the DSN at Epure. No Sentry Cloud account required. Only the open SDK client.
Official SDK, no proprietary agent
Install sentry-java (or keep it if you already have Sentry). Point dsn at Epure.
Self-host without a broker fleet
Postgres holds issues and events. No Kafka or Redis in the OSS compose. Self-host is a $0 software license; you still run the host. Cloud Pro is $29/mo, Scale is $89/mo.
Issues you can finish
Grouping, releases, alerts, and soft-sampling on spikes. Triage without a seat tax.
What the JVM hides
Service exceptions that never become a clean ticket.
Epure groups Java exceptions from HTTP and workers. Grouping uses raw frames, with no ProGuard symbol server.
Spring / servlet
Keep existing Sentry Spring integrations. Unhandled exceptions still post envelopes.
Workers & batch
Scheduled jobs and consumers share a project DSN or use a dedicated one.
Uncaught handlers
Thread default handlers that call captureException keep working after the host swap.
Breadcrumbs & tags
SDK scope data stays on the event for triage in the issue list.
Raw-frame stacks
No ProGuard / NDK symbolication. Grouping uses frames as sent.
Install path
Host. SDK. First issue.
New to Sentry or already on it. Same three moves. Official SDK in, DSN pointed at Epure, one test throw.
Run Epure
docker compose up locally (optional `.env` for ports). Register, name a project, copy the DSN from setup or Settings → SDK connection. Self-host is the path that ships today.
Install sentry-java
Add the official Sentry SDK from your package manager. Epure speaks the Sentry wire, so there is no @epure/* client.
Init and verify
Call Sentry.init with the Epure DSN. Throw once (or captureException). Confirm 202 and an issue in the list.
Wire path
Install the SDK. Point the DSN.
Fresh install or DSN swap: same init shape. Disable product lines Epure discards.
Install sentry-java
Official Sentry client from the package registry. No @epure/* SDK.
Point dsn at Epure
Paste the project DSN from Settings. Fresh install and Sentry migrants use the same field.
Disable discarded lines
Set traces, replay, and profile sample rates to 0. Epure stores exceptions only.
1# add io.sentry:sentry via Maven or GradleWhy Epure
The tracker that fits how you already run Java.
Check the fit before you paste the DSN.
Official SDK, no proprietary agent
Install sentry-java (or keep it if you already have Sentry). Point dsn at Epure.
Self-host without a broker fleet
Postgres holds issues and events. No Kafka or Redis in the OSS compose. Self-host is a $0 software license; you still run the host. Cloud Pro is $29/mo, Scale is $89/mo.
Issues you can finish
Grouping, releases, alerts, and soft-sampling on spikes. Triage without a seat tax.
Honest scope
Exceptions and stacks. We skip replay, profiling, and transaction APM, and never claim 100% compatibility.
Raw-frame grouping
Grouping uses file, function, and line as the SDK sends them. No ProGuard, dSYM, or NDK.
You own the data path
Self-host keeps stack traces on your Postgres. Cloud soft-samples instead of surprise invoices.
FAQ
Before you paste the Java DSN.
Do I need an existing Sentry Cloud account?
No. Install sentry-java from the package registry, create an Epure project, paste the DSN, and capture. You need their open SDK client, never their SaaS. Quickstart.
I already use sentry-java. Do I rewrite?
No. Leave the SDK. Change only the dsn to your Epure host. Set traces/replay/profile sample rates to 0 so you don’t ship volume Epure discards. Self-host install if you still need compose.
What about transactions, replay, and profiling?
Epure is exception tracking. Transactions are discarded. Replay and profiling items are ignored. Disable those sample rates in init.
How long until I see the first Java issue?
With Docker warm and a DSN in env, most people land a 202 and an issue the same sitting. Persistence is async, so under normal load an issue appears in well under a second.
Does Epure support ProGuard or Android?
No. There is no ProGuard, dSYM, or NDK symbolication. JVM services group on frames as sentry-java sends them. Spring Boot setup is /integrations/spring-boot. Android stays out of scope.
Point Java at Epure tonight.
Open the docs, compose up or Cloud, install the SDK, paste the DSN.
Apache 2.0 · official Sentry SDK · swap DSN