Independent. Self-hosted. Written in Go.
Error tracking and observability in Go. Run one application container with PostgreSQL and connect the Sentry SDKs you already use.
Active development · full parity still aheadTHE WORKSPACE
Group the errors. Read the stack.
Keep the context close.
WORKING TODAY
Independently implemented.
Verified against real clients and data.
Grouped issues keep stack traces, breadcrumbs, tags, affected users, comments and triage history together. Search and filters stay on durable event data.
JavaScript source maps, debug IDs and native symbol files connect minified or compiled frames back to useful source locations without discarding the original event.
Inspect transactions, standalone spans and child operations with latency percentiles, trace ancestry and cross-project waterfall views.
Search retained Sentry and OpenTelemetry logs by service, level, environment, time or trace. Inspect attributes without rounding 64-bit integers.
Schedule HTTP, TCP, SSL and heartbeat checks. Error-frequency and uptime rules deliver durable email, Slack, provider webhook or generic webhook attempts.
Invite members, manage owners, admins and teams, scope API tokens, attach projects to multiple teams and verify secondary sign-in emails.
Change the password with global session and token revocation, recover access by email, add verified secondary sign-in addresses, require a TOTP code from your authenticator app and use OIDC when configured.
MAKE IT YOURS
Pull the public application image and start it alongside PostgreSQL. No separate web or worker services to assemble.
You need Git, Docker with Compose, and OpenSSL.
Visit localhost:8000. The first start creates one owner and organization, so you land in the workspace; add a project and copy its DSN.
Copy the project DSN into your existing Sentry SDK configuration. Verify the capabilities your application needs.
git clone https://github.com/jerolan/good-sentry.git
cd good-sentry
test -f .env || printf 'SECRET_KEY=%s\n' "$(openssl rand -hex 32)" > .env
docker compose up -dKeep your .env between restarts. The secret protects sessions. Local mode has no login screen and is meant for a trusted machine or network; set GOODSENTRY_AUTH=required to enable sign-in, then configure your public domain and database credentials before exposing the stack.
A CLEAR STATUS
GoodSentry is an independent Go implementation in active development. Full Sentry compatibility and GlitchTip feature parity are not complete.
Error tracking, performance and typed logs, uptime and alerting, people and team management, verified account emails, optional TOTP two-factor sign-in, instance-wide OIDC plus per-organization OpenID Connect sign-in applications with a shareable login page, Sentry-compatible management APIs, minidump and DWARF/dSYM symbolication, Grafana Sentry data source panels and an opt-in MCP server with OAuth PKCE are implemented and tested. Vendor-specific provider deployments and external identity-provider receipts, automatic repository synchronization, advanced administration and the final requirement audit remain on the roadmap. OpenTelemetry log ingestion works through standard OTLP/HTTP exporters. Optional local/S3 Parquet cold span archival is queryable and retains spans through the configured transaction-retention deadline. Public amd64 and arm64 application images are available; a repeatable 2,100-request workload measured 34.47 MiB peak application memory with PostgreSQL excluded.