Sentry Known Pitfalls

Prerequisites

• Existing Sentry implementation to review

• Access to SDK configuration

• Understanding of current error patterns

• Codebase access for fixes

Instructions

• Verify SDK initialization happens before app starts

• Check for single initialization point (no multiple init calls)

• Use framework-specific SDK package for your framework

• Ensure Error objects are captured (not strings)

• Verify beforeSend returns event or null explicitly

• Check DSN is in environment variables (not hardcoded)

• Review sample rates for production appropriateness

• Verify all transactions call finish() in try/finally

• Check source map URL prefix matches actual URLs

• Review alert configuration for threshold-based rules (avoid alert fatigue)

Output

• Pitfalls identified in current setup

• Fixes applied for each issue

• Configuration validated

• Best practices checklist completed

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 Best Practices

• Troubleshooting Guide

Overview

Execute common Sentry pitfalls and how to avoid them.