Skip to content
Back to skills

Sentry Advanced Troubleshooting

ASecurity

Execute 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".

  • 2,688 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added February 7, 2026
code-qualityjavascriptjavabashdebuggingperformance

Works with

  • cli

Security analysis

A100/100

Pro scans all 9 files and shows the line behind each finding

Scanned February 12, 2026

npx -y skills add jeremylongshore/claude-code-plugins-plus-skills --skill sentry-advanced-troubleshooting --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Sentry Advanced Troubleshooting?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Sentry Advanced Troubleshooting
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/jeremylongshore-sentry-advanced-troubleshooting/badge)](https://www.skillsdirectory.com/skills/jeremylongshore-sentry-advanced-troubleshooting)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: "sentry-advanced-troubleshooting"
description: |
  Execute 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".
  
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

1. Enable debug mode in SDK configuration to see verbose logging
2. Verify SDK initialization by checking if client exists after init
3. Test network connectivity to Sentry ingest endpoint
4. Check sampling configuration to ensure events are not being dropped
5. Temporarily disable beforeSend filtering during debugging
6. Use sentry-cli sourcemaps explain to diagnose source map issues
7. Verify transaction creation and finish calls for performance data
8. Check breadcrumb capture with beforeBreadcrumb debugging
9. Resolve SDK conflicts by ensuring single initialization
10. 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.

## Resources
- [Sentry Troubleshooting](https://docs.sentry.io/platforms/javascript/troubleshooting/)
- [Source Maps Troubleshooting](https://docs.sentry.io/platforms/javascript/sourcemaps/troubleshooting/)

Files in this skill

  • SKILL.md1.8 KB
  • references/breadcrumbs-issues.md632 B
  • references/diagnostic-script.md976 B
  • references/errors.md466 B
  • references/events-not-appearing.md1.8 KB
  • references/examples.md199 B
  • references/performance-data-missing.md1.1 KB
  • references/sdk-conflicts.md764 B
  • references/source-maps-not-working.md1 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.