-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Next.js client monitoring not working in EU region #11559
Comments
Assigning to @getsentry/support for routing ⏲️ |
I assume you are using the |
Yes, we are using Here is request:
Second one:
Skipped ones return 200 from our server:
PS. you can try yourself from our QA env. Note: Sentry is not all the time there, because it's not yet merged to master. Yes, we have 7.109.0:
|
Interesting. These seem to be Session event payloads. If you trigger an error event, does it also get the 403 response? Also, can you try removing the |
Yeah, looks like only sessions return 403. Request:
|
@jkytomak In my previous message, I shared a screenshot of it working. Is it still broken for you? |
Ok now it stopped working for me again. Odd. |
Note: the same problem happens also on localhost. So should not be related to any aws infra. |
I forwarded this internally. I think I ruled out any SDK causes so it might be our infra or ingest pipeline. |
Tested locally without tunneling. It works fine (got first browser issue and replay to our DE org). |
@jkytomak the requests go to As for the sporadic 200 responses: The sentry point-of-presence server responds with status 200 opportunistically if it does not have information about the current project in its cache. |
We have sentry url configured only in Here is whole
|
Added this to sentry-webpack-plugin options: Note https://docs.sentry.io/platforms/javascript/guides/nextjs/manual-setup/ says:
|
I think we found the culprit. The matching logic based on the Fix is up here: #11577 |
@jkytomak Please disable tunnelRoute for now as a workaround until we have the fix released. Afterwards you can upgrade and the issue should be resolved. Thanks for reporting this and sticking with us. I'll make sure the release goes out on Monday first thing. |
I have the same issue using @sentry/browser. I migrated my projects from US to EU and it doesn't capture Web Vitals. The performance score is always 0. |
I have the same issue on 7.110.0, although it seems to be an ephemeral issue. I have seen it working in a small number of sessions. |
Hi again, yesterday we released version |
Works for us now. Thank you. |
Works for us now too. Thank you |
Hi, we are experiencing a similar problem using the |
@andreamaiolo could you open a new GH issue? We can investigate it from there, thanks! |
@andreamaiolo I think your particular problem relates to this issue getsentry/sentry#69089 posted by @billypap1 and not the one in this thread. |
Thank you both, I have opened this separate issue: #11646 We only encounter the problem when using the tunnel option. By deactivating it we see the INP parameter on the dashboard |
Environment
SaaS (https://sentry.io/)
Steps to Reproduce
Install sentry:
"@sentry/nextjs": "^7.109.0",
and create organization in EU region and point it there.
Next version in use is:
"next": "^12.3.4",
Expected Result
Client can send Sentry events via server to Sentry EU.
Actual Result
Server monitoring works fine, but client gets from
/api/monitoring
requests this response:If I change the client dsn to old US one, client monitoring works.
Product Area
Replays and Issues
Link
ORG_SLUG: humbol
DSN
No response
Version
No response
The text was updated successfully, but these errors were encountered: