Open segersniels opened 5 days ago
Hello @segersniels, thank you for writing in. We'll take a look at this.
@segersniels could you please provide a reproduction repo? I just ran through the steps provided and did not encounter any issue.
Could you also please provide more info on your environment, os, node version and such?
@segersniels could you please provide a reproduction repo? I just ran through the steps provided and did not encounter any issue.
Could you also please provide more info on your environment, os, node version and such?
Repository: https://github.com/segersniels/sentry-reproduce (mv .env.example .env
and replace SENTRY_DSN
)
$ node -v
v20.16.0
$ npm -v
10.8.1
Just worth mentioning that it's not just my machine. We've been trying to get this working in production at my company as well, so it's not really related to the OS I would think.
@segersniels
Thanks for the repro. It worked as expected as long as the env var was prefixed with NEXT_PUBLIC
, otherwise the dsn wasn't available on the client. I have also removed the myUndefinedFunction()
call to fix the build.
The error output you mentioned (Sentry Logger [error]: Could not find line 1264 ...
) comes from the Context Lines integration, which tries to add stack traces to the error (I agree that the output in this case can be very misleading, we'll try to fix that). If you want to disable it you could in theory just filter it out.
Back to your project: Do you actually run into the issue of Sentry not working as expected? e.g. do your errors show up in the issues page?
Thanks for the repro. It worked as expected as long as the env var was prefixed with NEXT_PUBLIC, otherwise the dsn wasn't available on the client. I have also removed the myUndefinedFunction() call to fix the build.
Sorry for that! The DSN was hardcoded after running the wizard and quickly changed some stuff around to create the repository like was asked. In our production environment this is not the case as they are also hardcoded there after running the wizard. So in my testing this was not even an issue.
Back to your project: Do you actually run into the issue of Sentry not working as expected? e.g. do your errors show up in the issues page?
No I can't get any error to show up in Sentry at all. Tried throwing errors in the middleware (edge), client, server, server actions, etc. Manual Sentry.captureMessage()
and stuff. I literally can't get anything to show up except for a few traces that always are just purely middleware related.
I do see failed transactions but no issues are popping up.
It just keeps showing this:
Yeah that should not be the case, can you show me your actual next.config
?
Yeah that should not be the case, can you show me your actual
next.config
?
Nearly identical as the one in the reproduction example as I can't get it working even with that config in the repo provided.
@segersniels I just noticed Sentry Logger [log]: Recording outcome: "ratelimit_backoff:error"
showing up in your logs. Which seems strange since you just started setting up this project? Can you check for https://docs.sentry.io/api/ratelimits/#headers in the response headers of your client?
@segersniels I just noticed
Sentry Logger [log]: Recording outcome: "ratelimit_backoff:error"
showing up in your logs. Which seems strange since you just started setting up this project? Can you check for https://docs.sentry.io/api/ratelimits/#headers in the response headers of your client?
I think we may have figured out what's going wrong!
We're in the midst of rewriting our entire application and didn't notice that our old application had started spamming errors 3 weeks ago and depleted our 5k error limit. We didn't think to check that far back and whether we had hit the limit.
Our account admin must have missed the email (if there was one). However our incompetence aside, I would have expected the SDK debug logging to clearly show us that this was the actual cause 🤔 From the debugging logging it just looked like everything was working fine except for a few ratelimit errors.
EDIT: Can confirm that once we upgraded our plan to the Team Plan we can now see the issues coming in!
Good to hear you're up and running 👍
My takeaway for this is:
I'll leave this ticket open for now so we can put it on our backlog!
I am having the similar experience - I created a fresh Next.js project using create-next-app
, then run npx @sentry/wizard@latest -i nextjs
. I enabled instrumentationHook
in Next config. I deployed this to Vercel.
Now, the errors from /sentry-example-page
ARE showing up, what is not working for me are API errors.
This is all I get:
I want to emphasize that it's not working in deployed environment - locally it's work just fine.
@branislavbrincko please set debug: true
to your sentry.server.config
, run a build locally (next build
), and start the app (next start
) – and then check the logs for any errors.
@branislavbrincko please set
debug: true
to yoursentry.server.config
, run a build locally (next build
), and start the app (next start
) – and then check the logs for any errors.
@chargome I am trying that and having another issue:
Not sure what this means :confused:
But again, as I mentioned, locally it works just fine, API errors appear in Sentry. Only when deployed on Vercel they don't appear.
Sorry my bad, you also need to set disableLogger: false
in your next.js.config
@chargome Thanks, I should have found that setting myself (though that message [Sentry] Cannot initialize SDK...
could be clearer).
Anyway... I turned on debug, built the app locally, started npm start
and accessed http://localhost:3000/api/sentry-example-api`. I see the following in the console (this error flows into Sentry):
When I deploy this (with logging enabled) to Vercel and I access /api/sentry-example-api on deployed environment, there's no [error] in my logs:
(Info logs - those I can see, so the logging is working:)
@branislavbrincko could you please provide a reproduction repo or stackblitz to investigate this further?
@andreiborza
Here is the repo: https://github.com/branislavbrincko/sentry-nextjs-test
It's plain Next.js app (using pages router though!) with Sentry inicialized via wizard.
Steps I did:
npx create-next-app@latest
(using pages
router!) npx @sentry/wizard@latest -i nextjs
https://<my-project-name>.vercel.app/sentry-example-page
and click Throw error!
buttonhttps://<my-project-name>.vercel.app/api/sentry-example-api
(NOTE: I am storing Sentry DNS in env variable NEXT_PUBLIC_SENTRY_DSN)
Result in Sentry (no API error appears here):
@branislavbrincko Thanks for pointing this out there seems to be an error with the pages api routes on vercel – we'll investigate.
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
8.34.0
Framework Version
React 18
Link to Sentry event
No response
Reproduction Example/SDK Setup
Been struggling to get Sentry working in a Next.js project I was working on. So I figured I would just try to recreate the issue step by step by starting from a clean slate and see what is preventing Sentry from tracking errors/issues. I created a completely fresh Next.js project through
npx create-next-app@latest
and then ran the wizard withnpx @sentry/wizard@latest -i nextjs
with the example included. So pretty much a completely barebones example. I was pretty stumped when I found out that even the most basic example wasn't working.Steps to Reproduce
npx create-next-app@latest
npx @sentry/wizard@latest -i nextjs
with example pageExpected Result
I would expect the issues to start showing up in sentry.io.
Actual Result