Agent skill · marketing growth · jeremylongshore
sentry-rate-limits
Manage Sentry rate limits, quotas, and event volume optimization.
Why this skill is useful
Provides specific Sentry configuration patterns and API usage that the AI wouldn't reliably generate on its own.
What it needs
Requires @sentry/node, sentry-sdk installed locally. Requires sentry account access. About 8k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
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 SENTRYAUTHTOKEN with org:read and project:write scopes (Settings > Auth Tokens) SENTRYORG and SENTRYPROJECT slugs known SDK 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 messages Transactions — performance monitoring spans Replays — session replay recordings Attachments — file uploads (crash dumps, minidumps) Profiles — continuous profiling data Cron monitors — scheduled job check-ins Rate limit headers returned on 429: Step 2 — Configure Client-Side Sampling Sampling is the first line of defense. Set sampleRate for errors and tracesSampleRate for performance transactions. TypeScript / Node.js: Python: 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. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/sentry-rate-limits