Sentry Cost Tuning
Prerequisites
- •Current Sentry billing plan known
- •Event volume metrics available
- •High-volume error sources identified
- •Cost reduction target defined
Instructions
- •Review current usage and cost breakdown by event type
- •Implement error sampling to reduce volume (e.g., 50% sampleRate)
- •Configure aggressive transaction sampling (1% or lower for high-volume)
- •Add ignoreErrors and denyUrls patterns for common noise
- •Enable server-side inbound filters in project settings
- •Set project rate limits to cap maximum events
- •Reduce event size with maxValueLength and maxBreadcrumbs limits
- •Disable unused features (replays, profiling) if not needed
- •Configure tiered environment settings (disable in dev, reduce in staging)
- •Set up spend alerts and monitor cost projections monthly
Output
- •Optimized sample rates
- •Event filtering rules
- •Cost projection updated
- •Spend alerts configured
Error Handling
See {baseDir}/references/errors.md for comprehensive error handling.
Examples
See {baseDir}/references/examples.md for detailed examples.