Sentry Performance Tuning

Prerequisites

• Performance monitoring enabled

• Transaction volume metrics available

• Critical paths identified

• Performance baseline established

Instructions

• Implement dynamic sampling with tracesSampler for endpoint-specific rates

• Configure environment-based sample rates (higher in dev, lower in prod)

• Remove unused integrations to reduce SDK overhead

• Limit breadcrumbs to reduce memory usage

• Use parameterized transaction names to avoid cardinality explosion

• Create spans only for meaningful slow operations

• Configure profile sampling sparingly for performance-critical endpoints

• Measure SDK initialization time and ongoing overhead

• Implement high-volume optimization with aggressive filtering

• Monitor SDK performance metrics and adjust configuration

Output

• Optimized sample rates configured

• SDK overhead minimized

• Transaction naming standardized

• Resource usage reduced

Error Handling

See ${CLAUDE_SKILL_DIR}/references/errors.md for comprehensive error handling.

Examples

See ${CLAUDE_SKILL_DIR}/references/examples.md for detailed examples.

Resources

• Sentry Performance

• Sampling Strategies

Overview

Optimize Sentry performance monitoring configuration.