communication observability ai_generated true

Sentry events silently dropped — rate limit or quota exceeded

ID: communication/sentry-event-dropped-rate-limit

Also available as: JSON · Markdown
85%Fix Rate
88%Confidence
4Evidence
2023-01-01First Seen

Version Compatibility

VersionStatusIntroducedDeprecatedNotes
any active — — —

Root Cause

Sentry drops events silently when project rate limit or org quota is exceeded.

generic

Workarounds

  1. 92% success Configure beforeSend to filter out noisy, low-value errors 
    Sentry.init({beforeSend(event) { if (event.message?.match(/ResizeObserver/)) return null; }})

    Sources: https://docs.sentry.io/platforms/javascript/configuration/filtering/

  2. 88% success Set per-key rate limits and use inbound filters 
    Project Settings > Client Keys > Rate Limits + Inbound Filters

    Sources: https://docs.sentry.io/product/accounts/quotas/manage-event-stream-guide/

Dead Ends

Common approaches that don't work:

  1. Increase Sentry plan quota blindly 60% fail

    The root cause is often noisy errors flooding the quota

  2. Disable rate limiting on the Sentry project 75% fail

    Without rate limits, a single noisy error can consume the entire org quota