-
-
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
Fastify / NodeJS tunnel does not seem to tunnel replays correctly #9582
Comments
Hey, In next.js, you can use the provided Did you just not find this option, or do you specifically want to use a custom tunnel instead? (This is not documented ideally everywhere in the docs yet, we'll look into this) In regard to your issue concretely, to be clear, is it also not working if you disable compression? That would be weird, because then nothing should be compressed and this should be straightforward enough... 🤔 Also just a note, you should definitely check the TBH I don't 100% know how your fastify + nest setup works together. Can it be that the content parser is not properly applied there, or something like this? |
We cannot use this option as I presume this will add a route to the next server, we however do a static export of our project and there will be no server present
Good news: After deleting all build caches, it seems to work when We have now upgraded our Nest Version to the
Definitely - I've stripped down the code to eliminate potential show-stoppers to debug this issue. I'm closing this and I hope somebody else will find it to be useful :) |
Ah, makes sense - thank you for the investigation work! Maybe somebody else will also run into this in the future 😅 |
Is there an existing issue for this?
How do you use Sentry?
Sentry Saas (sentry.io)
Which SDK are you using?
@sentry/browser
SDK Version
7.80.0
Framework Version
Node + Fastify (backend), @sentry/nextjs
Link to Sentry event
No response
SDK Setup
Backend setup
Fastify Setup
Sentry Controller (Nest)
Steps to Reproduce
tunnel
optiontunnel
option and setup backend according to https://github.com/getsentry/examples/blob/master/tunneling/fastify/index.jsExpected Result
Replays arrive at Sentry when using a tunnel
Actual Result
Replays do not arrive at Sentry when using a tunnel
Additional Information
{id: "sessionhash/eventhash"}
Sample request to tunnel capture from network tab
Response:
The text was updated successfully, but these errors were encountered: