Fresh install
Never used Sentry? Start here.
- 1. Compose up on your host
- 2. Install sentry-go
- 3. Init with the Epure DSN and verify
GoError tracking for Go with sentry-go
Epure is error tracking on two Compose containers. Go services still panic and return errors. Keep sentry-go. Set Dsn to your Epure host. Set tracing sample rates to 0. Flush before exit on short jobs. Verify Issues. Partial compat: no replay, APM, or profiling.
Host up → install SDK → paste DSN → confirm a 202.
Start here
From zero, or from Sentry.
Same finish line: sentry-go 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 Go.
Install sentry-go once. Point the DSN at Epure. No Sentry Cloud account required. Only the open SDK client.
Official SDK, no proprietary agent
Install sentry-go (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 Go hides
Panics and errors that never make the pager cleanly.
Epure groups Go exceptions from HTTP handlers and recover paths. Grouping uses raw frames.
Panics & recover
Middleware and recover hooks that call CaptureException still post envelopes to your DSN.
HTTP handlers
net/http, chi, and echo keep your existing sentry-go integrations. Swap the host, nothing else.
Workers & jobs
Background processes share the same project or use a dedicated DSN.
Flush before exit
Keep Flush on shutdown so short-lived jobs don’t drop the last event.
Raw-frame stacks
No Go symbol server. File, function, and line as sentry-go sends them.
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-go
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-go
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.
1go get github.com/getsentry/sentry-goWhy Epure
Install sentry-go. Point the DSN. Verify.
Keep the official SDK. Change only the host.
Official SDK, no proprietary agent
Install sentry-go (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 Go DSN.
Do I need an existing Sentry Cloud account?
No. Install sentry-go 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-go. 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 Go 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 demangle Go stacks?
No. There is no Go symbol server. Grouping uses file, function, and line as sentry-go sends them. Call Flush on shutdown so CLI jobs do not lose the last panic. Confirm a deliberate panic or CaptureException: HTTP 202, then an issue row (Verify).
Point Go at Epure tonight.
Compose up. Install sentry-go. Paste the DSN.
Apache 2.0 · official Sentry SDK · swap DSN