Skip to main content Início Criadores jeremylongshore claude-code-plugins-plus-skills sentry-rate-limits
sentry-rate-limits Manage Sentry rate limits, quotas, and event volume optimization.
Use when hitting 429 errors, tuning sampleRate/tracesSampleRate,
filtering noisy browser errors with beforeSend, configuring
inbound data filters, setting per-key rate limits, or monitoring
quota usage via the Sentry stats API.
Trigger: "sentry rate limit", "sentry quota", "reduce sentry events",
"sentry 429", "sentry spike protection", "sentry sampling".
Ir para a instalação Skills Marketplace Descubra e explore skills de IA criadas pela comunidade.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Mostrar detalhes do prompt Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.
npx skills add https://github.com/jeremylongshore/claude-code-plugins-plus-skills --skill sentry-rate-limitsO comando permanece em uma só linha. Role horizontalmente para revisá-lo antes de copiar.
Prefere uma cópia local? Baixe os arquivos disponíveis atualmente no SkillsMP.
Baixar Zip Baixando... Mais deste repositório Implement user sign-up and sign-in flows with Clerk.
Use when building authentication UI, customizing sign-in experience,
or implementing OAuth social login.
Trigger with phrases like "clerk sign-in", "clerk sign-up",
"clerk login flow", "clerk OAuth", "clerk social login".
Implement session management and middleware with Clerk.
Use when managing user sessions, configuring route protection,
or implementing token refresh and custom JWT templates.
Trigger with phrases like "clerk session", "clerk middleware",
"clerk route protection", "clerk token", "clerk JWT".
Configure enterprise SSO, role-based access control, and organization management.
Use when implementing SSO integration, configuring role-based permissions,
or setting up organization-level controls.
Trigger with phrases like "clerk SSO", "clerk RBAC",
"clerk enterprise", "clerk roles", "clerk permissions", "clerk organizations".
Ocupações relacionadas SOC
Baseado na classificação ocupacional SOC
Explorador de arquivos
4 arquivos name sentry-rate-limits description Manage Sentry rate limits, quotas, and event volume optimization.
Use when hitting 429 errors, tuning sampleRate/tracesSampleRate,
filtering noisy browser errors with beforeSend, configuring
inbound data filters, setting per-key rate limits, or monitoring
quota usage via the Sentry stats API.
Trigger: "sentry rate limit", "sentry quota", "reduce sentry events",
"sentry 429", "sentry spike protection", "sentry sampling".
allowed-tools Read, Write, Edit, Grep, Glob, Bash(curl:*), Bash(node:*), Bash(python3:*), Bash(pip:*) version 1.51.0 license MIT author Jeremy Longshore <jeremy@intentsolutions.io> tags ["saas","sentry","cost-optimization","rate-limiting","quotas","observability"] compatibility Designed for Claude Code, also compatible with Codex and OpenClaw
Sentry Rate Limits & Quota Optimization
Overview
Manage Sentry rate limits, sampling strategies, and quota usage to control costs without losing visibility into critical errors. Covers client-side sampling, beforeSend filtering, server-side inbound filters, per-key rate limits, spike protection, and the usage stats API.
Prerequisites
Sentry account with a project DSN configured
SENTRY_AUTH_TOKEN with org:read and project:write scopes (Settings > Auth Tokens)SENTRY_ORG and SENTRY_PROJECT slugs knownSDK installed: @sentry/node (npm) or sentry-sdk (pip)
Current event volume visible at sentry.io/stats/
Instructions
Step 1 — Understand Rate Limit Behavior
When your project exceeds its quota, Sentry returns 429 Too Many Requests with a Retry-After header. The SDK automatically stops sending events until the cooldown expires. Events generated during this window are permanently lost — there is no replay mechanism.
Rate limit tiers by plan:
Plan API Rate Limit Notes Developer 50 RPM Shared quota, no reserved volume Team 1,000 RPM Per-organization, includes spike protection Business 10,000 RPM Per-organization, custom quotas available Enterprise Custom Negotiated per contract
Quota categories (billed separately):
Errors — exceptions and log messagesTransactions — performance monitoring spansReplays — session replay recordingsAttachments — file uploads (crash dumps, minidumps)Profiles — continuous profiling dataCron monitors — scheduled job check-ins
Rate limit headers returned on 429:
HTTP/1.1 429 Too Many Requests
Retry-After: 60
X-Sentry-Rate-Limit-Limit: 50
X-Sentry-Rate-Limit-Remaining: 0
X-Sentry-Rate-Limit-Reset: 1711324800
Step 2 — Configure Client-Side Sampling Sampling is the first line of defense. Set sampleRate for errors and tracesSampleRate for performance transactions.
import * as Sentry from '@sentry/node' ;
Sentry .init ({
dsn : process.env .SENTRY_DSN ,
sampleRate : 0.25 ,
tracesSampleRate : 0.1 ,
tracesSampler : (samplingContext ) => {
const { name, parentSampled } = samplingContext;
if (parentSampled !== undefined ) return parentSampled;
if (name === 'GET /health' || name === 'GET /readiness' ) return 0 ;
if (name?.includes ('/health' )) return 0 ;
if (name?.includes ('/api/payment' ) || name?.includes ('/api/auth' )) return 1.0 ;
if (name?.startsWith ('GET /api/' ) || name?.startsWith ('POST /api/' )) return 0.2 ;
if (name?.startsWith ('GET /static/' ) || name?.startsWith ('GET /assets/' )) return 0 ;
return 0.05 ;
},
});
import sentry_sdk
def traces_sampler (sampling_context ):
tx_name = sampling_context.get("transaction_context" , {}).get("name" , "" )
if "/health" in tx_name or "/readiness" in tx_name:
return 0
if "/api/payment" in tx_name or "/api/auth" in tx_name:
return 1.0
if tx_name.startswith(("GET /api/" , "POST /api/" )):
return 0.2
if tx_name.startswith(("GET /static/" , "GET /assets/" )):
return 0
return 0.05
sentry_sdk.init(
dsn=os.environ["SENTRY_DSN" ],
sample_rate=0.25 ,
traces_sample_rate=0.1 ,
traces_sampler=traces_sampler,
)
Step 3 — Filter Noisy Errors with beforeSend Use beforeSend to drop events before they count against your quota. This runs client-side, so filtered events never reach Sentry.
Sentry .init ({
dsn : process.env .SENTRY_DSN ,
beforeSend (event, hint ) {
const error = hint?.originalException as Error | undefined ;
if (event.exception ?.values ?.some (e =>stacktrace ?.frames ?.some (f =>filename ?.includes ('extensions://' ) ||
f.filename ?.includes ('moz-extension://' ) ||
f.filename ?.includes ('chrome-extension://' )
)
)) {
return null ;
}
if (error?.message ?.match (/ResizeObserver loop/ )) return null ;
if (error?.message ?.match (/Non-Error promise rejection/ )) return null ;
if (error?.name === 'AbortError' ) return null ;
if (error?.message ?.match (/Load failed/ )) return null ;
if (error?.message ?.includes ('PaymentError' ) ||
event.tags ?.['transaction.type' ] === 'payment' ) {
return event;
}
return event;
},
ignoreErrors : [
'ResizeObserver loop completed with undelivered notifications' ,
'Non-Error promise rejection captured' ,
/Loading chunk \d+ failed/ ,
'Network request failed' ,
'Failed to fetch' ,
'AbortError' ,
/^Script error\.?$/ ,
'TypeError: cancelled' ,
'TypeError: NetworkError when attempting to fetch resource' ,
],
denyUrls : [
/extensions\//i ,
/^chrome:\/\//i ,
/^chrome-extension:\/\//i ,
/^moz-extension:\/\//i ,
/hotjar\.com/ ,
/google-analytics\.com/ ,
/googletagmanager\.com/ ,
/intercom\.io/ ,
],
});
def before_send (event, hint ):
if "exc_info" in hint:
exc_type, exc_value, _ = hint["exc_info" ]
if exc_type.__name__ in ("ConnectionResetError" , "BrokenPipeError" ):
return None
msg = str (exc_value)
if "health" in msg.lower() and "404" in msg:
return None
if event.get("tags" , {}).get("transaction.type" ) == "payment" :
return event
return event
sentry_sdk.init(
dsn=os.environ["SENTRY_DSN" ],
before_send=before_send,
ignore_errors=[
"ConnectionResetError" ,
"BrokenPipeError" ,
],
)
Step 4 — Enable Server-Side Inbound Data Filters Inbound filters run on Sentry's servers before quota counting. Filtered events do not consume quota — this is free filtering.
Configure at Project Settings > Inbound Filters :
Filter What it blocks Recommended Legacy browsers IE 9/10, old Safari, old Android Enable Browser extensions Errors from browser extension code Enable Localhost events Events from localhost / 127.0.0.1 Enable for production projects Web crawlers Bot-generated errors (Googlebot, etc.) Enable Filtered releases Specific release versions Use for deprecated releases Error message patterns Custom regex patterns Add known false-positive patterns
curl -X PUT \
-H "Authorization: Bearer $SENTRY_AUTH_TOKEN " \
-H "Content-Type: application/json" \
-d '{"active": true}' \
"https://sentry.io/api/0/projects/$SENTRY_ORG /$SENTRY_PROJECT /filters/legacy-browsers/"
curl -X PUT \
-H "Authorization: Bearer $SENTRY_AUTH_TOKEN " \
-H "Content-Type: application/json" \
-d '{"active": true}' \
"https://sentry.io/api/0/projects/$SENTRY_ORG /$SENTRY_PROJECT /filters/browser-extensions/"
curl -X PUT \
-H "Authorization: Bearer $SENTRY_AUTH_TOKEN " \
-H "Content-Type: application/json" \
-d '{"active": true}' \
"https://sentry.io/api/0/projects/$SENTRY_ORG /$SENTRY_PROJECT /filters/web-crawlers/"
Step 5 — Set Per-Key Rate Limits Each DSN (Client Key) can have its own rate limit. This prevents a single project from exhausting the organization's entire quota.
Configure at Project Settings > Client Keys > Configure > Rate Limiting .
curl -s -H "Authorization: Bearer $SENTRY_AUTH_TOKEN " \
"https://sentry.io/api/0/projects/$SENTRY_ORG /$SENTRY_PROJECT /keys/" \
| python3 -m json.tool
curl -X PUT \
-H "Authorization: Bearer $SENTRY_AUTH_TOKEN " \
-H "Content-Type: application/json" \
-d '{"rateLimit": {"window": 3600, "count": 1000}}' \
"https://sentry.io/api/0/projects/$SENTRY_ORG /$SENTRY_PROJECT /keys/$KEY_ID /"
Strategy for multi-environment setups:
Production DSN: 5,000 events/hour (critical errors matter)
Staging DSN: 500 events/hour (only need representative sample)
Development DSN: 100 events/hour (prevent local debugging floods)
Step 6 — Enable Spike Protection Spike protection is auto-enabled on Team and Business plans. It detects sudden event volume increases and temporarily rate-limits the project to prevent quota exhaustion from error storms.
Configure at Organization Settings > Spike Protection .
When spike protection triggers:
Sentry detects volume exceeding 10x normal baseline
Events are temporarily dropped (429 returned to SDK)
An email notification is sent to organization owners
Protection auto-disables after the spike subsides
For programmatic spike alerts, set up a Sentry alert rule:
Condition: Number of events in project exceeds thresholdAction: Send notification to Slack/PagerDuty/emailFrequency: Alert once per hour
Step 7 — Monitor Quota Usage via API
curl -s -H "Authorization: Bearer $SENTRY_AUTH_TOKEN " \
"https://sentry.io/api/0/organizations/$SENTRY_ORG /stats_v2/?field=sum(quantity)&groupBy=category&interval=1d&statsPeriod=7d" \
| python3 -m json.tool
curl -s -H "Authorization: Bearer $SENTRY_AUTH_TOKEN " \
"https://sentry.io/api/0/organizations/$SENTRY_ORG /stats_v2/?field=sum(quantity)&groupBy=project&category=error&interval=1d&statsPeriod=7d" \
| python3 -m json.tool
curl -s -H "Authorization: Bearer $SENTRY_AUTH_TOKEN " \
"https://sentry.io/api/0/organizations/$SENTRY_ORG /stats_v2/?field=sum(quantity)&groupBy=outcome&category=error&interval=1d&statsPeriod=24h" \
| python3 -m json.tool
Step 8 — Reduce Payload Size and Deduplicate Reduce event size and improve grouping to lower quota consumption:
Sentry .init ({
dsn : process.env .SENTRY_DSN ,
maxBreadcrumbs : 30 ,
maxValueLength : 500 ,
beforeSend (event ) {
if (event.request ?.data && typeof event.request .data === 'string' ) {
event.request .data = event.request .data .substring (0 , 1000 );
}
if (event.request ?.cookies ) delete event.request .cookies ;
if (event.exception ?.values ?.[0 ]) {
const { type , value } = event.exception .values [0 ];
const normalized = value
?.replace (/\b[0-9a-f]{8}(-[0-9a-f]{4}){3}-[0-9a-f]{12}\b/gi , '<UUID>' )
?.replace (/\b\d+\b/g , '<N>' ) || '' ;
event.fingerprint = [type || 'unknown' , normalized];
}
return event;
},
});
Output After completing these steps, you will have:
Sampling rates configured (sampleRate, tracesSampleRate, tracesSampler) to reduce event volume while preserving visibility into critical paths
beforeSend filtering dropping noisy browser errors (ResizeObserver, AbortError, extension errors) before they count against quotaignoreErrors and denyUrls patterns blocking known false positivesServer-side inbound filters enabled for free pre-quota filtering
Per-key rate limits set to prevent single-project quota exhaustion
Spike protection enabled and alert rules configured
Quota monitoring via the /stats_v2/ API endpoint
Custom fingerprinting reducing event duplication
Error Handling Error Cause Solution 429 Too Many RequestsQuota exhausted for current billing period Lower sampleRate and tracesSampleRate, add patterns to ignoreErrors, enable per-key rate limits Events silently dropped Client SDK respecting Retry-After header Reduce volume at source; SDK auto-recovers after cooldown expires Critical errors missed sampleRate too lowUse beforeSend to force-return critical errors regardless of sampling; never filter payment/auth errors Quota exhausted early in period No per-project rate limits Set hourly rate limits per client key to spread quota evenly across the billing period Spike consuming entire quota Spike protection not enabled or threshold too high Enable spike protection in organization settings; set up volume alert rules 401 Unauthorized on stats APIInvalid or expired auth token Regenerate token at Settings > Auth Tokens with org:read scope Inbound filter not reducing volume Filter configured but wrong error type Verify filter targets correct category; browser extension filter only works for JS SDK errors tracesSampler not calledtracesSampleRate takes precedence in some SDK versionsRemove tracesSampleRate when using tracesSampler — they conflict
Examples
Example 1 — Quota Monitoring Bash Script #!/usr/bin/env bash
set -euo pipefail
ORG="${SENTRY_ORG:?Set SENTRY_ORG} "
TOKEN="${SENTRY_AUTH_TOKEN:?Set SENTRY_AUTH_TOKEN} "
THRESHOLD=${QUOTA_THRESHOLD:-80}
accepted=$(curl -s -H "Authorization: Bearer $TOKEN " \
"https://sentry.io/api/0/organizations/$ORG /stats_v2/?field=sum(quantity)&groupBy=outcome&category=error&statsPeriod=1h&interval=1h" \
| python3 -c "
import json, sys
data = json.load(sys.stdin)
for g in data.get('groups', []):
if g['by'].get('outcome') == 'accepted':
print(g['totals']['sum(quantity)']); break
else: print(0)" )
echo "Accepted events (last hour): $accepted "
[ "$accepted " -gt "$THRESHOLD " ] && echo "WARNING: volume $accepted > threshold $THRESHOLD "
Example 2 — Enable All Inbound Filters via API #!/usr/bin/env bash
set -euo pipefail
BASE="https://sentry.io/api/0/projects/$SENTRY_ORG /$SENTRY_PROJECT /filters"
AUTH="Authorization: Bearer $SENTRY_AUTH_TOKEN "
for filter in legacy-browsers browser-extensions web-crawlers; do
curl -s -X PUT -H "$AUTH " -H "Content-Type: application/json" \
-d '{"active": true}' "$BASE /$filter /" && echo "Enabled: $filter "
done
Resources
Next Steps
Cost review : Query /stats_v2/ weekly to track spend trends by categoryAlert rules : Create Sentry alerts for volume spikes per projectReplay sampling : Apply replaysSessionSampleRate and replaysOnErrorSampleRate for session replay cost controlServer-side sampling : Explore Sentry Dynamic Sampling (server-side) for organization-wide policiesAudit ignoreErrors : Review quarterly — patterns may suppress real bugs as code evolves 