sentry-common-errors

Troubleshoot common Sentry integration issues and fixes.Use when encountering Sentry errors, missing events,or configuration problems.Trigger with phrases like "sentry not working", "sentry errors missing","fix sentry", "sentry troubleshoot".

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

When & Why to Use This Skill

This Claude skill is a specialized diagnostic tool designed to troubleshoot and resolve common Sentry integration issues. It streamlines the debugging process for developers by identifying root causes for missing events, configuration errors, and source map mismatches, ensuring that application monitoring remains reliable and accurate.

Use Cases

  • 1. Resolving Missing Events: Diagnose why application errors are not appearing in the Sentry dashboard by verifying DSN settings, environment variables, and beforeSend logic.
  • 2. SDK Configuration Audit: Automatically check for correct SDK initialization, including debug mode activation and breadcrumb integration settings.
  • 3. Source Map & Release Troubleshooting: Fix unreadable stack traces by verifying that source maps are correctly uploaded and matched with the appropriate release versions.
  • 4. Performance & Volume Optimization: Review and adjust tracesSampleRate and ignoreErrors patterns to manage event quotas and reduce noise in monitoring data.
namesentry-common-errors
description|
allowed-toolsRead, Grep, Bash(npm:*), Bash(curl:*)
version1.0.0
licenseMIT
authorJeremy Longshore <jeremy@intentsolutions.io>

Sentry Common Errors

Prerequisites

  • Sentry SDK installed
  • Debug mode enabled for troubleshooting
  • Access to Sentry dashboard
  • Application logs available

Instructions

  1. Enable debug mode in SDK configuration for verbose output
  2. Verify DSN is set correctly in environment variables
  3. Check beforeSend function returns event (not undefined)
  4. Review sampling rates to ensure events are not being dropped
  5. Verify source maps are uploaded with correct release version
  6. Set user context after authentication for user tracking
  7. Add ignoreErrors patterns for noisy errors to reduce volume
  8. Enable Breadcrumbs integration with appropriate options
  9. Set tracesSampleRate greater than 0 for performance monitoring
  10. Run diagnostic commands to verify connectivity and capture

Output

  • Issue root cause identified
  • Configuration fix applied
  • Error capture verified working
  • Documentation of resolution

Error Handling

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

Examples

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

Resources