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 ${CLAUDE_SKILL_DIR}/references/errors.md for comprehensive error handling.
Examples
See ${CLAUDE_SKILL_DIR}/references/examples.md for detailed examples.
Resources
-
Sentry Troubleshooting
-
Source Maps Troubleshooting
Overview
Execute advanced Sentry troubleshooting techniques.