sentry-known-pitfalls

Common Sentry pitfalls and how to avoid them.Use when troubleshooting Sentry issues, reviewing configurations,or preventing common mistakes.Trigger with phrases like "sentry mistakes", "sentry pitfalls","sentry common issues", "sentry anti-patterns".

⭐878stars🔀101forks📁View on GitHub🕐Updated Jan 4, 2026

When & Why to Use This Skill

This Claude skill optimizes Sentry implementations by identifying and resolving common configuration pitfalls and anti-patterns. It streamlines troubleshooting, ensures accurate error capturing, and validates best practices for SDK initialization, source maps, and alert configurations to enhance system observability and reliability.

Use Cases

  • 1. Sentry Configuration Audit: Automatically review existing SDK setups to ensure environment-based DSNs, framework-specific packages, and proper initialization sequences are correctly implemented.
  • 2. Error Capture Optimization: Debug issues where Error objects are not being captured correctly or where 'beforeSend' logic is improperly filtering out critical events.
  • 3. Observability & Performance Tuning: Validate transaction handling and production sample rates to ensure reliable performance monitoring without excessive overhead or data loss.
  • 4. Alert Fatigue Management: Review and refine alert rules and thresholds to ensure the engineering team receives actionable notifications rather than system noise.
namesentry-known-pitfalls
description|
allowed-toolsRead, Write, Edit, Grep
version1.0.0
licenseMIT
authorJeremy Longshore <jeremy@intentsolutions.io>

Sentry Known Pitfalls

Prerequisites

  • Existing Sentry implementation to review
  • Access to SDK configuration
  • Understanding of current error patterns
  • Codebase access for fixes

Instructions

  1. Verify SDK initialization happens before app starts
  2. Check for single initialization point (no multiple init calls)
  3. Use framework-specific SDK package for your framework
  4. Ensure Error objects are captured (not strings)
  5. Verify beforeSend returns event or null explicitly
  6. Check DSN is in environment variables (not hardcoded)
  7. Review sample rates for production appropriateness
  8. Verify all transactions call finish() in try/finally
  9. Check source map URL prefix matches actual URLs
  10. 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 {baseDir}/references/errors.md for comprehensive error handling.

Examples

See {baseDir}/references/examples.md for detailed examples.

Resources