Using tunnel and processing events without DSN

After following the docs on how to make use of the tunnel option, and setting this up successfully (most events are successfully forwarded), I noticed we still receive quite some events which cannot be forwarded as there is no DSN header present.

The body of these events look something like this:


What is the purpose of these events and how should these be processed?

Ah, this looks like a bug with a newly introduced client_reports feature. Will report this to the team, thanks a lot!

The fix is coming fix(browser): Send client outcomes through tunnel if configured by kamilogorek · Pull Request #4031 · getsentry/sentry-javascript · GitHub Thanks for reporting this.

No problem, thank you for the swift response and fix.