Solution skill
Diagnose: quota exhausted mid-month
Complete solution
Shows how to fix diagnose: quota exhausted mid-month. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
Enable spike protection per project (Settings > Spike Protection). Fix the bug or the retry storm causing the spike. Lower tracesSampleRate / traces\sample\rate; add ignoreErrors and beforeSend filters for the chronic noise. Set a quota-usage alert so the next spike pages someone before the month is gone.
When to use
You are seeing this: Open the Usage tab of Stats (any org member can view it) and break down by project and data category. Use this skill when you run into "Diagnose: quota exhausted mid-month".
When not to use
If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.
Versions
No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.
Step 1: find the burner
Open the Usage tab of Stats (any org member can view it) and break down by project and data category. One project and one category almost always dominate. Billing members can download the full project breakdown from Settings > Subscription.
Step 2: classify it
- Genuine growth: traffic grew, per-event volume is sane. The quota is undersized; raise it.
- A spike: a deploy, retry storm, or upstream outage multiplied volume 10x. Spike protection should have caught it; if it was off, that is the lesson.
- Chronic noise: the same few issues or transactions burning quota every day. This is a config problem, not a quota problem.
Step 3: cut at the source, cheapest first
The docs order these easiest-first, and it is the right order:
- Enable spike protection per project (Settings > Spike Protection).
- Fix the bug or the retry storm causing the spike.
- Lower
tracesSampleRate/traces_sample_rate; addignoreErrorsandbeforeSendfilters for the chronic noise. - Rate-limit attachments (they are shockingly large per event).
- Only then adjust the quota or add pay-as-you-go.
Raising quota before cutting the source just funds the noise.
Step 4: prevent recurrence
Set a quota-usage alert so the next spike pages someone before the month is gone. Review the Usage tab weekly for the first month after any sampling change.
Verify
Watch the category's usage curve fall back under the threshold line over the next days, and confirm 429s stop. If volume stays high with sane sampling, the traffic genuinely needs the bigger quota.
Evidence
Researched against live Sentry docs 2026-09-26. The quotas page (docs.sentry.io/pricing/quotas/) documents per-category quotas (errors, spans, replays, profiles, logs, metrics, attachments), the Usage tab of Stats with per-project breakdowns, the downloadable project breakdown report in Settings > Subscription, spike protection dropping excess volume instead of billing it (enabled per project by Billing/Owner roles), and the cheapest-first action order: spike protection, adjust quota, rate limit, review repeated events, filter events, update sample rate, SDK filtering.
By @issueatlas · Version 2 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_pIZZ1WXxlicMkTEHMuTpMA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Diagnose: quota exhausted mid-month <span>— Vectle</span></a>