Use this skill when working with Sentry - error monitoring, performance tracing, session replay, cron monitoring, alerts, or source maps. Triggers on any Sentry-related task including SDK initialization, issue triage, custom instrumentation, uploading source maps, configuring alerts, and integrating Sentry into JavaScript, Python, Next.js, or other supported frameworks.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.
Instruções da origem · Visualização somente leitura
name
sentry
version
0.1.0
description
Use this skill when working with Sentry - error monitoring, performance tracing, session replay, cron monitoring, alerts, or source maps. Triggers on any Sentry-related task including SDK initialization, issue triage, custom instrumentation, uploading source maps, configuring alerts, and integrating Sentry into JavaScript, Python, Next.js, or other supported frameworks.
[{"url":"https://docs.sentry.io/","accessed":"2026-03-14T00:00:00.000Z","description":"Main documentation hub and navigation structure"}]
license
MIT
maintainers
[{"github":"maddhruv"}]
When this skill is activated, always start your first response with the 🧢 emoji.
Sentry
Sentry is an application monitoring platform that provides real-time error tracking,
performance monitoring, session replay, and cron job monitoring. It captures errors
and exceptions with full stack traces, groups them into issues for triage, and provides
distributed tracing to debug performance bottlenecks across your stack. Sentry supports
20+ platforms with dedicated SDKs for JavaScript, Python, Go, Ruby, Java, and more.
When to use this skill
Trigger this skill when the user:
Wants to set up Sentry in a new or existing project (any SDK)
Needs to configure error monitoring, tracing, or session replay
Asks about Sentry SDK initialization options (DSN, sample rates, integrations)
Wants to upload source maps for readable stack traces
Needs to set up alerts (issue, metric, uptime, or cron alerts)
Asks about custom instrumentation - creating spans, setting context, or breadcrumbs
Wants to integrate Sentry with Next.js, Django, Flask, Express, or other frameworks
Needs to configure the Sentry CLI for releases or CI/CD
Do NOT trigger this skill for:
General application logging unrelated to Sentry (use observability skill instead)
Error handling patterns or try/catch best practices without Sentry context
DSN (Data Source Name) is the unique identifier for your Sentry project. It tells
the SDK where to send events. Found in Settings > Projects > Client Keys.
Events vs Issues: An event is a single error occurrence or transaction. Sentry
automatically groups similar events into issues using fingerprinting. Your quota is
consumed by events, not issues.
Issue states: Issues flow through unresolved -> resolved (or ignored/archived).
Resolved issues that recur become regressed. Archived issues exceeding forecast
volume become escalating.
Traces, transactions, and spans: A trace is a complete request flow across services.
A transaction is a top-level span representing a user-facing operation. Spans are the
smallest unit of work (DB queries, HTTP calls, file I/O). Distributed tracing connects
spans across services via trace propagation headers.
Session Replay: Records DOM state, user interactions, network requests, and console
logs as a video-like reproduction. Privacy-first: masks all text and media by default.
Common tasks
Initialize Sentry in Next.js
Use the wizard for automatic setup of client, server, and edge configs:
npx @sentry/wizard@latest -i nextjs
This creates instrumentation-client.ts, instrumentation.ts, sentry.server.config.ts,
sentry.edge.config.ts, and wraps next.config.ts with withSentryConfig:
Sentry.init({
dsn: "...",
tracesSampleRate: 0.1, // 10% of transactions// Or use a function for dynamic samplingtracesSampler: (samplingContext) => {
if (samplingContext.name.includes("/health")) return0;
if (samplingContext.name.includes("/api/checkout")) return1.0;
return0.1;
},
});
Gotchas
Sentry.init() must be the very first import - If any other module (logging, HTTP client, database driver) is imported before Sentry.init() runs, that module's errors and performance data will not be captured. In Node.js, put Sentry.init() in a dedicated instrument.js file that is required before anything else via --require.
tracesSampleRate: 1.0 in production will exhaust quota fast - 100% tracing on any meaningful traffic volume rapidly burns through your event quota and skews billing. Use tracesSampler with a function that returns 0 for health checks and static assets, and lower rates (0.1-0.2) for general traffic.
Source maps must be uploaded before the first error - Source map artifacts are matched to errors by release version. If an error is ingested before the source maps for that release are uploaded, the stack trace is permanently unminified in the UI. Upload source maps as part of the deploy pipeline, before traffic is shifted.
Session Replay records sensitive data by default without explicit masking - While maskAllText: true is the default, custom components that inject text via innerHTML or canvas elements are not automatically masked. Audit replay recordings in a staging environment before enabling in production on pages with PII.
withSentryConfig in Next.js wraps and rewrites next.config.js - If you manually merge config options incorrectly, you can silently disable Sentry's webpack instrumentation. Always use the spread pattern for nextConfig and verify source map upload in CI output after setup.
Error handling
Error
Cause
Resolution
Invalid DSN
Malformed or missing DSN string
Verify DSN in Settings > Projects > Client Keys
Rate limited (429)
Exceeding project or org event quota
Reduce sample rates or increase quota in billing
Source maps not applied
Missing debug IDs or upload timing
Run wizard, verify production build, upload before deploy
CORS errors on tunnel
Misconfigured tunnel route
Set tunnelRoute: "/monitoring" in Next.js config
Events not appearing
SDK not initialized early enough
Move Sentry.init() to the very first import/line
References
For detailed content on specific sub-domains, read the relevant file
from the references/ folder:
references/sdk-configuration.md - Complete SDK options for JavaScript and Python
references/nextjs-setup.md - Full Next.js integration guide with all config files
references/api-cli.md - Sentry REST API and CLI reference
Only load a references file if the current task requires it - they are
long and will consume context.
Companion check
On first activation of this skill in a conversation: check which companion skills are installed by running ls ~/.claude/skills/ ~/.agent/skills/ ~/.agents/skills/ .claude/skills/ .agent/skills/ .agents/skills/ 2>/dev/null. Compare the results against the recommended_skills field in this file's frontmatter. For any that are missing, mention them once and offer to install:
