Agent skill · software engineering · jeremylongshore
sentry-load-scale
Scale Sentry for high-traffic applications handling millions of events
Why this skill is useful
Provides specific adaptive sampling strategies and SDK performance optimizations for Sentry that are not commonly known.
What it needs
Requires @sentry/node installed locally. Requires sentry account access. About 9k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Sentry Load & Scale Overview Configure Sentry for applications processing 1M+ requests/day without sacrificing error visibility, burning through quota, or adding measurable SDK overhead. Covers adaptive sampling, connection pooling, multi-region tagging, quota management, SDK benchmarking, batch submission, load testing, and self-hosted deployment considerations. Prerequisites Application handling sustained high traffic (>10K requests/min or >1M events/day) Sentry organization with quota and billing access (Settings > Subscription) @sentry/node v8+ installed (npm ls @sentry/node) Performance baseline established (p50/p95/p99 latency without Sentry) Event volume estimates calculated per category (errors, transactions, replays, attachments) Instructions Step 1 — Implement Adaptive Sampling Static tracesSampleRate wastes quota at scale because it treats a health check the same as a checkout. Replace it with a traffic-aware tracesSampler that adjusts rates based on endpoint criticality and current load. Traffic-aware tracesSampler: Adaptive error deduplication with beforeSend: Step 2 — Optimize SDK for Minimal Overhead At high throughput, every byte and every millisecond of SDK processing matters. This configuration reduces memory footprint, payload size, and CPU time. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/sentry-load-scale--c07e39