You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Max drop limit for TelemetryEventBuffer after which we completely drop events (#2831)
* Have a higher max limit for TelemetryEventBuffer after which we
completely drop events
* This is mainly to protect from memory blowup in high throughput
scenarios
* Also raised the Metric buffer limits to 1k/10k as compared to 100/1k
for logs (consistent with Python)
* Update sentry-ruby/spec/sentry/configuration_spec.rb
Co-authored-by: Peter Solnica <peter@solnica.online>
---------
Co-authored-by: Peter Solnica <peter@solnica.online>
Copy file name to clipboardExpand all lines: CHANGELOG.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -60,6 +60,7 @@
60
60
61
61
- Unify Logs and Metrics implementations ([#2826](https://github.com/getsentry/sentry-ruby/pull/2826))
62
62
- Unify LogEventBuffer and MetricEventBuffer logic ([#2830](https://github.com/getsentry/sentry-ruby/pull/2830))
63
+
- Add maximum limits on LogEventBuffer (1k) and MetricEventBuffer (10k) for protection from memory blowup ([#2831](https://github.com/getsentry/sentry-ruby/pull/2831))
0 commit comments