Using tunnel and processing events without DSN

On-Premise
1

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:

{}
{"type":"client_report"}
{"timestamp":1633415835.655,"discarded_events":[{"reason":"sample_rate","category":"transaction","quantity":1}]}

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

2

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

3

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.

4

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

5

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.