Connect Go with its Sentry SDK
Your Go app keeps its Sentry SDK. Xovris gives it your project’s DSN, and every error it sends becomes a Xovris issue with its stack and release.
go get github.com/getsentry/sentry-goAlready installed? Your code stays as it is – the DSN is the one change.
Start it
Put this at the top of main():
// reads SENTRY_DSN from the environmentif err := sentry.Init(sentry.ClientOptions{}); err != nil { log.Fatalf("sentry.Init: %s", err)}defer sentry.Flush(2 * time.Second)It reads SENTRY_DSN, so your project’s address never sits in your code.
Your project’s DSN
Xovris finds the SDK in your go.mod, creates your project’s address and writes it as SENTRY_DSN in your env file, after showing you the change. It then sends a test event and waits until it is stored. In the project, run:
npx xovris@latest initSee the first error
Send one from anywhere your app runs:
sentry.CaptureException(errors.New("first error for Xovris"))Capture one error with the SDK’s own call and it appears as a Xovris issue:
- Errors and their stack traces, grouped into issues
- Messages you capture
- The release each event names
Its frameworks
The same DSN covers every framework this SDK’s own integrations reach:
Echo, FastHTTP, Fiber, Fiber v3, Gin, gRPC, Iris, Negroni and net/http.
What Xovris has run
Driven with the real SDK: sentry-go 0.50.0, captured 2026-11-13 (a bare exception list, a recovered panic). Its own bytes are replayed into Xovris on every change.
Every option the SDK has is in its own documentation: docs.sentry.io/platforms/go/
Traces and metrics too
Xovris also sets Go up with OpenTelemetry for traces, metrics and logs beside the SDK’s errors. Connect Go (net/http) with OpenTelemetry
Your data is never used to train our AI. How your data is kept
A problem is called fixed only once it works again. How each fix is checked
XOVRIS LTD, registered in England and Wales, company number 17499910. Registered office: 66 Paul Street, London EC2A 4NA.