Repository navigation
In Next.js-project, errors inside pages/api not caught by Sentry when deployed on Vercel #11708
Description
Is there an existing issue for this?
- I have checked for existing issues https://github.com/getsentry/sentry-javascript/issues
- I have reviewed the documentation https://docs.sentry.io/
- I am using the latest SDK release https://github.com/getsentry/sentry-javascript/releases
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
Activity
s1gr1d commentedon Apr 22, 2024
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
init? If you haven't already, you need to set up theinitfunction insentry.server.(js|ts)to make it work on the server-side.Danane84 commentedon Apr 22, 2024
Hi Sigrid, thanks for your quick reply!
I set up Sentry by using the wizard. My
initis located insentry.server.config.jsinside the root-directory of my project and looks as follows:Liebe Grüße von Wien nach Wien ;)
s1gr1d commentedon Apr 22, 2024
Servus!
This setup seems correct so far. Some additional things you could check:
SENTRY_DSNvariable defined?debug: true)