Agent skill · data analytics · jeremylongshore
sentry-performance-tuning
Optimize Sentry performance monitoring for lower overhead and higher
Why this skill is useful
Provides specific configuration patterns and performance tuning techniques for Sentry that the AI wouldn't reliably generate on its own.
What it needs
Requires sentry-cli installed locally. Requires sentry account access. About 7k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Sentry Performance Tuning Overview Optimize Sentry's performance monitoring pipeline to maximize signal quality while minimizing SDK overhead and event volume costs. Covers the v8 SDK API for @sentry/node, @sentry/browser, and sentry-sdk (Python), targeting sentry.io or self-hosted Sentry 24.1+. Prerequisites Sentry SDK v8+ installed (@sentry/node >= 8.0.0 or sentry-sdk >= 2.0.0) Sentry.init() called with a valid DSN before any application code runs Performance monitoring enabled (tracesSampleRate > 0 or a tracesSampler function) Access to the Sentry Performance dashboard to verify changes Instructions Step 1 — Replace Static tracesSampleRate with Dynamic tracesSampler A flat tracesSampleRate: 0.1 samples all routes equally. The tracesSampler callback makes per-transaction decisions based on route, operation type, and upstream trace context. Step 2 — Configure Profiling with profilesSampleRate The profilesSampleRate controls what fraction of traced transactions get profiled. Setting it to 1.0 with a 5% tracesSampler means 5% of traffic is profiled. Tuning: Start at profilesSampleRate: 0.1 in production. Profiling adds ~3-5% CPU overhead per profiled transaction. Continuous profiling (profileSessionSampleRate) has lower per-transaction cost but runs on sampled instances continuously. Step 3 — Fix Transaction Naming (Prevent Cardinality Explosion) Names with dynamic IDs (/api/users/12345) create thousands of unique entries, degrading dashboard performance and inflating quota. Route templates go in the name, dynamic values go in attributes. Detect cardinality issues with a Discover query: Step 4 — Add Custom Measurements Custom measurements appear in the Performance dashboard and can be charted, alerted on, and queried in Discover. Unit types: 'millisecond', 'byte', 'none' (count), 'percent'. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/sentry-performance-tuning