# Next.js Error Monitoring & Performance Monitoring

> Catch failures across the App Router, React Server Components, middleware, and edge — including the production-only ones you cannot reproduce locally.

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

---

**Documentation:** [https://docs.sentry.io/platforms/javascript/guides/nextjs/](https://docs.sentry.io/platforms/javascript/guides/nextjs/)

## FAQ

**Why logs in Sentry?**

When debugging, logs, traces, and errors work better together. Logs provide the granular context—like retries, API failures, and internal state—that spans and errors can miss. But in most tools today, logs live in a separate system, forcing you to switch between tools to piece together the full picture.

With[logs in Sentry](https://sentry.io/product/logs/), everything is in one place. You can see logs right alongside your errors and traces—no more context switching, just faster debugging.

**Do you have log and trace drains?**

Yes. Send logs and traces without code changes to Sentry from platforms where you can't use the Sentry SDKs. [Set up log drains](https://docs.sentry.io/product/drains/) to forward logs from your deployments directly to Sentry without code changes. Log drains are available for [Vercel](https://docs.sentry.io/product/drains/vercel/), [Cloudflare](https://docs.sentry.io/product/drains/cloudflare/), [Heroku](https://docs.sentry.io/product/drains/heroku/), [Supabase](https://docs.sentry.io/product/drains/supabase/), and [Shopify Hydrogen](https://docs.sentry.io/product/drains/shopify-hydrogen/).

**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](https://sentry.io/pricing/).

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

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.

**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/).

**Does Sentry monitor uptime?**

Yes. Sentry Uptime Monitoring checks your critical URLs on a schedule and alerts you when they stop responding, so you find out before your users do. Downtime is correlated with the errors and traces from the same window, so you can go straight from "the site is down" to the code that broke it.

Learn more about [Uptime Monitoring](/product/uptime-monitoring/) and [Cron Monitoring](/product/cron-monitoring/).

---

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