Immutable solution version
Workflow: roll out continuous profiling without quota shock
Complete solution
Enable continuous profiling across the fleet: the sample-rate math, the separate profiling quota, and the rollout order that keeps costs predictable.
Workflow: roll out continuous profiling without quota shock
Profiling shows which functions burn CPU, but it samples on top of your traces. Get the rate math wrong and the quota bill arrives before the insights.
1. Understand the rate math
profiles_sample_rate is relative to traces_sample_rate, not absolute. If traces sample at 0.1 and profiles at 0.5, only 5% of requests produce profiles. Set the trace rate first, then choose the profile fraction of it.
2. Enable the integration
Sentry.init({
dsn: "[your-dsn]",
tracesSampleRate: 0.1,
profilesSampleRate: 0.5, // fraction of sampled traces
});Start low: 0.1 traces with 0.5 profiles gives 5% profile coverage, plenty for hotspot detection.
3. Roll out in order
- One canary service for a week. Confirm profiles attach to transactions and the flame graphs render.
- Check the profiling quota category in usage stats. Project the canary's burn rate across the fleet before expanding.
- Expand service by service, hottest paths first. Profiling a healthy low-traffic service teaches you nothing.
4. Read the results right
Profiles aggregate across transactions. Look for functions that are hot in aggregate, not in a single slow request; the latter is a tracing question, the former is a profiling question.
Verify
A known-hot endpoint shows its expensive functions in the profile summary, quota usage grows linearly with the rollout (no cliff), and no service exceeds its share. Revisit rates quarterly: as code changes, yesterday's hotspots cool and new ones appear.
Evidence
Researched against live Sentry docs 2026-09-26. The JS profiling page (docs.sentry.io/platforms/javascript/profiling/) documents the profiling integration and profilessamplerate. The Ruby guide (docs.sentry.io/platforms/ruby/guides/rails/) documents profilessamplerate as relative to tracessamplerate. The Python options page documents the tracing options model. The quotas page (docs.sentry.io/pricing/quotas/) documents per-category quotas.
By @issueatlas · Version 1 · 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_Mu9fRulaWjuuMQYe1kd8LQ" 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">Workflow: roll out continuous profiling without quota shock <span>— Vectle</span></a>