Go Error Tracking | Self-hosted

Supported Go frameworks and libraries

Because Telebugs is fully compatible with the official Sentry Go SDK, it works with the entire Sentry Go ecosystem out of the box.

• Standard Go — Any net/http or custom server. Initialize the SDK early in main.
• Gin — Use the sentrygin integration for automatic request context.
• Echo — sentryecho for Echo framework support.
• Chi, Fiber, and others — Standard middleware patterns work with minor adaptation.
• Any Go application — CLI tools, workers, gRPC services, or cloud functions. Just init the SDK with your Telebugs DSN.

For the complete and up-to-date list of supported integrations, see the Sentry Go documentation. The integration code is identical when sending data to Telebugs.

Easy install for Go teams

Telebugs itself is designed to be trivial to run on your own infrastructure.

If you can run a single terminal command, you can set up Telebugs. The whole process takes less than 10 minutes for most people. Once it’s running, you point your Go apps at it and start capturing real production errors.

See the installation guide for Docker, systemd, and other deployment options. It works great on small VPS instances and ARM hardware.

How to integrate Telebugs with Go

Use the official github.com/getsentry/sentry-go package. The only difference from Sentry is the DSN.

go get github.com/getsentry/sentry-go

Initialize it early in your application (typically in main, before starting your server):

import (
	"github.com/getsentry/sentry-go"
)

func main() {
	err := sentry.Init(sentry.ClientOptions{
		Dsn: "https://your-telebugs-instance.com/api/v1/sentry_errors/1234",
		// Enable performance monitoring if needed
		// TracesSampleRate: 1.0,
	})
	if err != nil {
		log.Fatalf("sentry.Init: %s", err)
	}
	// ...
}

For framework-specific extras, use the corresponding package:

go get github.com/getsentry/sentry-go/gin

Then use the middleware (see the Sentry Go Gin docs for examples). The integration works identically with Telebugs.

Once set up, Telebugs will automatically capture panics and errors, and you can add manual breadcrumbs, tags, and user context exactly as you would with Sentry.

Full options are documented in the Sentry Go docs. Everything works the same with Telebugs.

Background tasks and concurrency

Go teams often use goroutines, workers, or queues like Asynq or Machinery. Telebugs captures errors from these when you use the Sentry Go SDK with proper context propagation.

Errors that occur in goroutines or background jobs are reported with the same rich context as HTTP handlers. Use sentry.WithScope or pass the hub for isolation. This is especially valuable for long-running services where issues are hard to reproduce locally.

See the Sentry Go docs for concrete examples with goroutines and workers.

Releases and artifacts for Go

Go stack traces are usually readable, but using releases still gives you valuable context: which version introduced a regression, the ability to associate errors with deploys, and clearer debugging in production.

Use the Sentry CLI or the releases API to create releases during your deployment process (e.g., with go build and version info). See the releases and sourcemaps guide for details.

What you gain with Telebugs for Go

Go developers using Telebugs typically highlight:

• Strong default grouping that works well for Go stack traces and reduces duplicate noise.
• Flexible notifications (email, push, Slack, Discord, Teams, webhooks) with rules so you only get paged for real problems.
• Full control over data retention and the ability to run completely offline.
• Predictable one-time cost instead of per-event billing that can explode with high-traffic APIs or background jobs.
• Simple operation: one container, low resource usage, easy to keep updated.

You keep the excellent Sentry Go SDK developer experience while running a much lighter server-side system.

Frequently asked questions about Telebugs and Go

Does Telebugs work with goroutines and background jobs?

Yes. When you use the Sentry Go SDK with proper hub/scope propagation, errors raised in goroutines or background workers are reported automatically with the surrounding context.

Can I use Telebugs with any Go version?

Telebugs is compatible with the versions supported by the official Sentry Go SDK. Most teams are on Go 1.18+ these days; check the Sentry docs for the exact matrix.

Do I get the same context as Sentry?

Yes for core error tracking. You receive the full stack trace, local variables (when enabled), request data, breadcrumbs, tags, user info, and extras. Features that are outside pure error tracking (such as full performance tracing or session replays) are not part of Telebugs’ scope.

How do I handle sensitive data in Go errors?

Use the Sentry Go SDK’s BeforeSend or other scrubbing options, or Telebugs’ server-side sensitive data scrubbing rules. You stay in full control because everything runs on your infrastructure.

Ready to track Go errors on your own terms?

Read the Telebugs manual, the Sentry SDK compatible guide, or get Telebugs and point your Go apps at it today.