# Go (Golang) Error & Performance Monitoring

> Recover from panics and trace slow requests across net/http, Gin, Echo, Fiber, and gRPC, with full stack traces and readable source context.

**URL:** https://sentry.io/for/go/

---

Debug Go apps and prevent crashes across your entire stack. Trace Go performance issues back to a poor performing API call and surface any related code errors. Sentry provides a single platform to optimize the performance of Go code and deliver fast customer experiences.

**Documentation:** [https://docs.sentry.io/platforms/go/](https://docs.sentry.io/platforms/go/)

## Features

### Go Error Monitoring With Complete Stack Traces

See details like filename and line number so you never have to guess with Go errors. Filter and group Go exceptions intuitively to eliminate noise. Monitor errors at scale without impacting throughput in production.

### Fill In The Blanks

Reproduce errors without user feedback. Sentry's Go error monitoring includes each bug's history of events and actions.

### Understand The Bigger Picture

Use issue graphs to understand frequency, scope, and impact of Go errors and prioritize what needs to be fixed. Get alerts via email, SMS, or chat when bugs make it into production without disrupting your development workflow.

### Your Logs, Next to the Trace

Send structured logs from your Go services to Sentry and query them alongside your [traces](/product/tracing/) and errors. The log lines emitted during a failed request are attached to that request, giving you the retries and internal state that a stack trace alone cannot show.

Learn more about [Logs in Sentry](/product/logs/).

## FAQ

**What is the difference between Sentry and traditional logging?**

Traditional logging provides you with a trail of events. Some of those events are errors, but many times they're simply informational. Sentry is fundamentally different because we focus on exceptions, or in other words, we capture application crashes. We discuss in more detail [here](/vs/logging/) and on our [blog](https://blog.sentry.io/lets-get-ready-to-monitor/).

**What  languages does Sentry support?**

Sentry supports every major  language, framework, and library. You can browse each of them [here](/platforms/).

**How much does Sentry cost?**

You can get started for free. Pricing depends on the number of monthly events, transactions, and attachments that you send Sentry. For more details, visit our [pricing page](/pricing/).

**How does Sentry impact the performance of my app?**

Sentry doesn't impact a web site's performance.

If you look at the configuration options for when you initialize Sentry in your code, you'll see there's nothing regarding minimizing its impact on your app's performance. This is because our team of SDK engineers already developed Sentry with this in mind.

Sentry is a listener/handler for errors that asynchronously sends out the error/event to Sentry.io. This is non-blocking. The error/event only goes out if this is an error.

Global handlers have almost no impact as well, as they are native APIs provided by the browsers.

**Which Go frameworks does Sentry support?**

The Sentry Go SDK ships integrations for the `net/http` standard library, Gin, Echo, Fiber (v2 and v3), Iris, Negroni, FastHTTP and gRPC, so you can capture errors and traces without hand-rolling middleware.

The SDK recovers from panics, captures full stack traces with source context, and supports [Logs](/product/logs/) and [Cron Monitoring](/product/cron-monitoring/) for scheduled work.

**Can I send logs to Sentry?**

Yes. Sentry Logs lets you send, view, and query structured logs from your application alongside your errors and traces. Because logs sit next to the error and the trace that produced them, you get the granular context — retries, API failures, internal state — that spans and stack traces alone can miss, without switching tools.

Learn more about [Logs in Sentry](/product/logs/).

**What is Seer, Sentry's AI debugging agent?**

Seer is Sentry's AI debugging agent. It reads the full context Sentry already has — the error, its stack trace, the surrounding trace, logs, and profiles — to find the root cause of an issue and propose a fix. Seer can open a pull request with that fix, hand the work to an external coding agent, or review your PRs before they ship.

Learn more about [Seer](/product/seer/) and [Autofix](/product/seer/autofix/).

---

*Source: [sentry.io/for/go/](https://sentry.io/for/go/)*