Decide which Sentry signal to reach for when instrumenting code — error, span, span attribute, log, or metric. Use when adding instrumentation and unsure whether something should be a log vs a span vs a metric, when deciding "what to instrument where", when reviewing instrumentation for gaps, or when a coding agent needs a rule for choosing between errors, traces, logs, and metrics.
安装
npx skills add getsentry/sentry-for-ai --skill sentry-instrumentation-guidenpx skills add getsentry/sentry-for-ai --skill sentry-instrumentation-guide -a claude-code -gnpx skills add getsentry/sentry-for-ai --skill sentry-instrumentation-guide -a codex -ggemini skills install https://github.com/getsentry/sentry-for-ai.git --path skills-legacy/sentry-instrumentation-guidegh skill install getsentry/sentry-for-ai sentry-instrumentation-guidegit clone --depth 1 https://github.com/getsentry/sentry-for-ai /tmp/getsentry__sentry-for-ai
mkdir -p ~/.claude/skills ~/.agents/skills
cp -R /tmp/getsentry__sentry-for-ai/skills-legacy/sentry-instrumentation-guide ~/.claude/skills/sentry-instrumentation-guide # Claude Code
cp -R /tmp/getsentry__sentry-for-ai/skills-legacy/sentry-instrumentation-guide ~/.agents/skills/sentry-instrumentation-guide # Codex, Cursor, Gemini CLI, Copilot, OpenCode