Error monitoring
Get actionable insights to resolve the most important code-related issues. Track, debug, and resolve errors across any language or framework with tailored context to get to the root cause every time.
Tolerated by 4 million developers.
Fix broken code fast
Avoid wasting time reproducing errors. Get context like the line of code, user actions, and functions leading up to the error to debug and fix it fast.
Know when your code fails and who can help fix it. Automatically assign issues to the developer that introduced the broken code, and notify your team through Slack when the error happens the first time, reoccurs, or worsens.
Get immediate visibility across releases with insights into core metrics like crash-free sessions, version adoption, and failure rates. Know when a release starts to degrade so you can revert quickly… if you have to.
Getting started with Sentry is simple
We support every technology (except the ones we don't).
Get started with just a few lines of code.
Just run this commmand to sign up for and install Sentry.
npx @sentry/wizard@latest -i nextjs
Enable Sentry Tracing by adding the below code.
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.
- browser info
- reference to specific line of code
- specific error with tracing (through to backend)
This doesn't even cover session replays!
I’m beginning to realize that having Sentry ultimately results in better UX because you fix so many of these papercuts you didn’t know you have.
Know the who, what, why behind broken code
Get the code-level context you need to fix issues that matter most