Closed bruno-garcia closed 1 year ago
Hmm, interesting. What would be a reasonable way to debounce this from your POV? Just drop any such breadcrumb if there was one in the last second, or in a longer time period, e.g. 10 seconds?
Hmm, interesting. What would be a reasonable way to debounce this from your POV? Just drop any such breadcrumb if there was one in the last second, or in a longer time period, e.g. 10 seconds?
That sounds good to me. I don't have strong feelings on this one, just think this is a best effort in telling the dev the "site is heavy and can potentially have issues" but we shouldn't do that in a way that gets too noisy.
I don't think we should drop breadcrumbs unless we sum up the mutations when debouncing, otherwise the significance of the mutation breadcrumbs will get lost.
Just saw this extreme case:
We talked this over and came out with 2 potential solutions:
1) Handle this on the UI side - this keeps SDK simpler and also allows the UI to handle this more generically across other crumbs if we wanted.
2) On the SDK, we should consider flushing based on event buffer size instead of only time. This way a massive event-build up won't result in lost events due to segment size
Closing in favor of https://github.com/getsentry/sentry/issues/54688
On websites with lots of mutations this can be spammy:
Consider debouncing it