Problem Statement
When setting up the tunnel option, users will often follow the docs and add a local API route to forward those envelopes.
These POST requests will usually get auto-instrumented on the backend and will potentially result in a transaction for every frontend envelope.
Solution Brainstorm
Filter these out in some way?
If the tunnel option is set in the frontend, we could automatically set the Content-Type as application/x-sentry-envelope. This can be picked up in the http instrumentation and used to ignore these requests.
Problem Statement
When setting up the
tunneloption, users will often follow the docs and add a local API route to forward those envelopes.These POST requests will usually get auto-instrumented on the backend and will potentially result in a transaction for every frontend envelope.
Solution Brainstorm
Filter these out in some way?
If the
tunneloption is set in the frontend, we could automatically set theContent-Typeasapplication/x-sentry-envelope. This can be picked up in the http instrumentation and used to ignore these requests.Content-Typeheader will also fix a Svelte issue Feedback widget with screenshot via tunnelling not working #16112