-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
[@sentry/nextjs] api route transaction bleed still happening #3913
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
Comments
I wonder if we should actually be using AsyncLocalStorage: https://nodejs.org/api/async_context.html |
Just to confirm, I moved all my |
I can confirm that we've the same problem with the setup from the documentation:
One thing we don't do because it doesn't seem to be necessary is that we don't import |
This issue has gone three weeks without activity. In another week, I will close it. But! If you comment or otherwise update it, I will reset the clock, and if you label it "A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀 |
I suspect this bug that this fixes may be to blame: #4086. We should release a new version (which will be 6.13.4) in the next few days, which will include that fix. Once that happens, can you please let us know if you're still having problems? |
Having the same issue here using the latest version 6.14.3. Any updates on this? @lobsterkatie |
This issue has gone three weeks without activity. In another week, I will close it. But! If you comment or otherwise update it, I will reset the clock, and if you label it "A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀 |
Uh oh!
There was an error while loading. Please reload this page.
Our infra pings our Next.js API Route
GET /api/healthz
before each deployment goes live.For some reason, every event after this shows up in Sentry associated with this transaction.
It looks like domains were supposed to prevent this from happening (#3788 and #3574) but we're seeing it consistently.
Possibly related, to keep our files DRY we define our withSentry (amongst other things like auth etc) in a file that is imported and used by each API Route:
Our code definitely returns a new instance of withSentry() but I wonder if domains are not able to clearly differentiate?
The text was updated successfully, but these errors were encountered: