-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
In Next.js-project, errors inside pages/api not caught by Sentry when deployed on Vercel #11708
Comments
Hello, thanks for reaching out! Did you use the wizard for setting up Sentry or did you set it up manually? Where did you set up |
Hi Sigrid, thanks for your quick reply! I set up Sentry by using the wizard. My
Liebe Grüße von Wien nach Wien ;) |
Servus! This setup seems correct so far. Some additional things you could check:
|
Is there an existing issue for this?
How do you use Sentry?
Sentry Saas (sentry.io)
Which SDK are you using?
@sentry/nextjs
SDK Version
7.111.0
Framework Version
Next.jsj 13.5.6
Link to Sentry event
No response
SDK Setup
Sentry.init({
dsn: SENTRY_DSN,
// Adjust this value in production, or use tracesSampler for greater control
tracesSampleRate: 1,
// Setting this option to true will print useful information to the console while you're setting up Sentry.
debug: false,
});
Steps to Reproduce
Create a Next.js app, add Sentry, deploy on Vercel
Expected Result
Errors from the pages/api folder are reported in Sentry, when deployed on Vercel
Actual Result
Errors from the pages/api folder are not reported in Sentry, when deployed on Vercel
The text was updated successfully, but these errors were encountered: