Error Monitoring for Developers
Don’t waste cycles reproducing errors. Trace errors across your entire stack and act fast with all the context you need to fix the root cause - like the line of code, user actions and functions leading up to when it occurred.
Know when your code breaks and who can help fix it. Quickly know how many real users experienced the error, auto-assign issues to who committed the broken code, and alert your team over communication channels like Slack when an error happens the first time, regresses or escalates.
Get real-time visibility across releases to see core metrics like crash-free sessions, version adoption, and failure rate so you can see the moment a release starts to degrade and quickly take action.
Getting started is simple
We support every technology (except the ones we don't).
Get started with a few lines of code.
Just run this commmand to sign up for and install Sentry.
npx @sentry/wizard@latest -i nextjs
That's it. Be sure to 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 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
Get monthly product updates from Sentry
Sign up for our newsletter.
And yes, it really is monthly. Ok, maybe the occasional twice a month, but for sure not like one of those daily ones that you just tune out after a while.
Fix it
Get started with the only application monitoring platform that empowers developers to fix application problems without compromising on velocity