Next.js Error and Performance Monitoring
Actionable insights to resolve Next.js performance bottlenecks and errors. Improve your monitoring workflow with a full view of releases so you can mark Next.js errors as resolved and prioritize live issues.
Jamstack June
A month of Sentry product updates, help sessions, and tips to improve your app experience.
Deploy and Monitor Next.js applications with Sentry & Netlify
Join us as we walk through how to build, deploy, and monitor Next.js applications.
Register nowSentry Application Monitoring for Next.js
Capture errors, measure performance, configure suspect commits, and automatically upload sourcemaps with zero(-ish) configuration.
Read moreWant free Sentry? Tell a friend.
Give 3 months Sentry and get 3 months free. It might be awkward, but their users will thank you.
Refer a friendAutomate Sentry Releases with Netlify
Learn how to automate release management and deliver a reliable customer experience with Sentry and Netlify.
Read moreUnminify JS and more with Sentry and Vercel
Our integration with Vercel automtically generates releases, configures suspect commits, and uploads source maps for you.
Read moreJamstack Monitoring with Strapi and Sentry
Check out how how you can automatically send errors encountered in your React and Strapi application
Watch nowGetting Started is Simple
Sentry captures data by using an SDK within your application’s runtime.
npm install --save @sentry/nextjsConfigure your DSN:
npx @sentry/wizard -i nextjsThat’s it. There’s no step three. Don’t believe us? Check out our Documentation.
See all platforms
Next.js Error Monitoring with Complete Stack Traces
See the error and Next.js stack trace previously only visible in your user’s debug console. Apply source maps automatically to convert minified, compiled, or transpiled code back to its original form. Keep your Next.js source maps private by uploading them directly to Sentry.
Next.js Performance Monitoring
Within minutes after installing Sentry, software teams are able to trace Next.js performance issues back to a poor performing API call as well as surface all related code errors. Engineering Managers and Developers now have a single tool to optimize the performance of their code and deliver fast customer experiences.
Fill In the Blanks About Next.js Errors
See what the app was doing when the Next.js error occurred: user interactions, AJAX requests, console log messages and more. When frontend errors happen, Sentry can prompt users for feedback so you can compare their experiences to the data.
“We were able to catch errors with Sentry before customers could report them or before they hit our support queue.”
Debugging Any Next.js Exception
Record environment and usage details so you can recreate bugs down to the browser version, OS, and query parameters specific to the session.
Sentry’s tag distribution graph also makes it easy to isolate and prioritize any Next.js error by seeing how often it occurs in context.
Answer the most important questions: Was the bug browser or OS specific? Firefox or Safari?
You can’t afford to put JavaScript monitoring on the backburner.
Even a one-second delay in loading results in a 7% reduction in conversions.
Forty percent of customers abandon a website that takes longer than three seconds to load.
The average cost of downtime is $5,600 per minute — or $300,000 per hour.
FAQs
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.