1
Per-issue event cap: drop after N occurrences, keep counting
Source: getsentry/sentry#116339 · opened by @sentry-junior[bot]
Per-issue event cap: drop after N occurrences, keep counting: Sentry's rate limits operate at the project level and drop events entirely — including their contribution to an issue's occurrence count. There's no way to cap event storage for a specific noisy issue while still knowing its true occurrence frequency.
No pledges yet. Be the first to back this.
Comments
Similar requests
Feature request: apply sampling only after N occurrences
3 votes · 0 comments
Apply error-message inbound filters to minidumps
0 votes · 0 comments
[Replay] SSE (text/event-stream) response body not captured - 0B recorded despite successful stream
0 votes · 0 comments
Support event-driven PR comments for newly captured errors (including open and draft PRs)
0 votes · 0 comments
Spike Protection: Minimum Event Calculation capes project count to 5, even when having 100 projects in contract - flexibility needed
8 votes · 0 comments
No comments yet.