Commit ec43b68
authored
fix(core): Stop sending client reports for breadcrumbs (#24537)
This PR removes the `{ reason: 'buffer_overflow', category: 'log_item'
}` client report the SDK sent when the breadcrumbs buffer (100
breadcrumbs limit) overflowed and we evicted breadcrumbs.
Why? When we started working on logs, we [wanted to
know](getsentry/team-sdks#116) how many
breadcrumbs we currently discard due to the 100 crumbs limit. We used
the new `log_item` data category for this and `buffer_overflow` reason.
Later on, we added client reports for actual log discards and re-used
this data category but sent different reasons. Meaning different
telemtry items now fall into the same discard bucket as reported in
#24510.
Since I don't think we still need to know about breadcrumb discards, and
they're not their own telemetry items but part of errror and transaction
events, I think we can just stop emitting client reports for them.
closes #245101 parent ad0965f commit ec43b68
2 files changed
Lines changed: 0 additions & 17 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
574 | 574 | | |
575 | 575 | | |
576 | 576 | | |
577 | | - | |
578 | 577 | | |
579 | 578 | | |
580 | 579 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
357 | 357 | | |
358 | 358 | | |
359 | 359 | | |
360 | | - | |
361 | | - | |
362 | | - | |
363 | | - | |
364 | | - | |
365 | | - | |
366 | | - | |
367 | | - | |
368 | | - | |
369 | | - | |
370 | | - | |
371 | | - | |
372 | | - | |
373 | | - | |
374 | | - | |
375 | | - | |
376 | 360 | | |
377 | 361 | | |
378 | 362 | | |
| |||
0 commit comments