sentry-advanced-troubleshooting
Advanced Sentry troubleshooting techniques.Use when debugging complex SDK issues, missing events,source map problems, or performance anomalies.Trigger with phrases like "sentry not working", "debug sentry","sentry events missing", "fix sentry issues".
When & Why to Use This Skill
The Sentry Advanced Troubleshooting skill is designed to streamline the resolution of complex Sentry SDK integrations and error-tracking issues. It provides automated diagnostic workflows for fixing missing events, resolving source map mismatches, and correcting performance monitoring anomalies. By leveraging advanced debugging techniques and Sentry CLI tools, this skill ensures your application's observability pipeline is accurate, reliable, and fully optimized for production monitoring.
Use Cases
- Diagnosing Missing Events: Systematically verify SDK initialization, network connectivity to Sentry endpoints, and event sampling configurations to ensure all critical errors are captured.
- Source Map Troubleshooting: Resolve issues with unminified code and broken stack traces by using diagnostic scripts to validate source map uploads and alignment.
- Performance Data Validation: Audit transaction creation and breadcrumb capture to fix anomalies in performance metrics and ensure accurate latency reporting.
- SDK Conflict Resolution: Identify and resolve configuration conflicts or multiple initialization issues that prevent the Sentry client from functioning correctly.
| name | "sentry-advanced-troubleshooting" |
|---|---|
| description | | |
| allowed-tools | "Read, Write, Edit, Grep, Bash(cmd:*)" |
| version | 1.0.0 |
| license | MIT |
| author | "Jeremy Longshore <jeremy@intentsolutions.io>" |
Sentry Advanced Troubleshooting
Prerequisites
- Debug mode enabled in SDK
- Access to application logs
- Sentry dashboard access
- Sentry CLI installed for source map debugging
Instructions
- Enable debug mode in SDK configuration to see verbose logging
- Verify SDK initialization by checking if client exists after init
- Test network connectivity to Sentry ingest endpoint
- Check sampling configuration to ensure events are not being dropped
- Temporarily disable beforeSend filtering during debugging
- Use sentry-cli sourcemaps explain to diagnose source map issues
- Verify transaction creation and finish calls for performance data
- Check breadcrumb capture with beforeBreadcrumb debugging
- Resolve SDK conflicts by ensuring single initialization
- Run diagnostic script to generate comprehensive health report
Output
- Root cause identified for SDK issues
- Source map problems resolved
- Event capture verified working
- Performance monitoring validated
Error Handling
See {baseDir}/references/errors.md for comprehensive error handling.
Examples
See {baseDir}/references/examples.md for detailed examples.