SDK Logo

Error and Performance Monitoring for Next.js

Automatically capture errors and performance bottlenecks with clear, actionable debugging context for your Next.js app—across client, server, and edge components.

Video thumbnail

Next.js monitoring that's "not bad"

Video thumbnail

Get detailed stack traces and debugging context for every error—without having to ask for screenshots of the users console. De-minify your code while keeping source maps  private and connect issues across your Next.js app. Session Replay shows exactly what led up to an issue, helping you debug hydration errors, navigation failures, layout shifts, and user frustration signals like rage clicks and dead clicks.

Video thumbnail

Trace requests from client-side interactions through RSCs, server actions, and edge functions. Get precise context down to the line of broken code to:

  • Pinpoint slow or failing server actions without sifting through logs

  • Track database queries that slow down API responses

  • Catch middleware failures affecting authentication and redirects

  • Monitor edge function timeouts impacting user experience

Video thumbnail

Sentry spots the bottlenecks that are impacting real users like:

  • Rendering delays from inefficient hooks and effects

  • Unnecessary re-renders that degrade performance

  • Slow API responses from server-side functions

  • Blocking middleware increasing response times

Video thumbnail

With Codecov, get clear insights into your Next.js app’s coverage and test performance.

  • Identify gaps in API route and component test coverage

  • Spot flaky tests causing CI/CD failures

  • Ensure critical functionality like authentication and routing is well-tested

Getting started is simple

Just run this command to sign up for and install Sentry.

Click to Copy
npx @sentry/wizard@latest -i nextjs

Enable Sentry Tracing by adding the below code.

Click to Copy
import * as Sentry from '@sentry/nextjs'; Sentry.init({ dsn: 'https://examplePublicKey@o0.ingest.sentry.io/0', // We recommend adjusting this value in production, or using tracesSampler // for finer control tracesSampleRate: 1.0, });

That's it. Check out our documentation to ensure you have the latest instructions.

FAQs

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 and on our blog.

Sentry supports every major frontend language, framework, and library. You can browse each of them here.

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.

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.

Of course we have more content

Fix It

Get started with the only application monitoring platform that empowers developers to fix application problems without compromising on velocity.