Individual skill
sentry-advanced-troubleshooting
Advanced Sentry troubleshooting for complex SDK issues, silent event drops, source map failures, distributed tracing gaps, and SDK conflicts. Use when events silently disappear, source maps fail to resolve, traces break across service boundaries, or the SDK conflicts with other libraries like OpenTelemetry or winston. Trigger with phrases like "sentry events missing", "sentry source maps broken", "sentry debug", "sentry not capturing errors", "sentry tracing gaps", "sentry memory leak", "sentry sdk conflict".
skills/.curated/sentry-advanced-troubleshooting/SKILL.md
Source commit 0500b275e963c027f6b410e8c49c0446945c574e
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 12, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 2,917
- Repository last updated
- Nov 12, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai Repository topic
- automation Repository topic
- claude-code Repository topic
- devops Repository topic
- mcp Repository topic
- ai-agents Repository topic
- anthropic Repository topic
- claude-code-plugins Repository topic
- developer-tools Repository topic
- llm Repository topic
- saas Declared skill tag
- sentry Declared skill tag
- debugging Declared skill tag
- troubleshooting Declared skill tag
- source-maps Declared skill tag
- distributed-tracing Declared skill tag
- sdk-conflicts Declared skill tag
- testing Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 14,948 bytesSKILL.mdcore · 14,948 bytesSKILL.mdcore · 14,948 bytesSKILL.mdcore · 14,948 bytesSKILL.mdcore · 14,948 bytesSKILL.mdcore · 14,948 bytesSKILL.mdcore · 14,948 bytesSKILL.mdcore · 14,948 bytesSKILL.mdcore · 14,948 bytesSKILL.mdcore · 14,948 bytesSKILL.mdcore · 14,948 bytesSKILL.mdcore · 14,948 bytesreferences/breadcrumbs-issues.mddoc · 635 bytesreferences/diagnostic-script.mddoc · 977 bytesreferences/errors.mddoc · 620 bytesreferences/events-not-appearing.mddoc · 1,867 bytesreferences/examples.mddoc · 353 bytesreferences/performance-data-missing.mddoc · 1,101 bytesreferences/sdk-conflicts-network-transport.mddoc · 11,169 bytesreferences/sdk-conflicts.mddoc · 768 bytesreferences/source-maps-not-working.mddoc · 1,053 bytes
Read excerpt
# Sentry Advanced Troubleshooting
## Overview
This skill addresses complex Sentry issues that go beyond basic setup: events that silently drop, source maps that refuse to resolve, distributed traces with gaps between services, SDK memory leaks, conflicts with other observability libraries, and network-level DSN blocking. Each section provides a systematic diagnosis path with concrete commands and code to identify root causes.
## Prerequisites
- Sentry SDK v8 installed and initialized (see `sentry-install-auth` skill)
- Access to application logs, Sentry dashboard, and project settings
- Sentry CLI installed (`npm install -g @sentry/cli`) for source map debugging
- Network diagnostic tools available (curl, dig)
- `debug: true` enabled in SDK init for verbose console output during troubleshooting
## Instructions