Terminal
Terminal/Skill
Adds Sentry to an app or turns on one more signal, such as tracing, logging, profiling, session replay, cron check-ins or AI agent monitoring.
By Sentry
Works with
npx skills add getsentry/sentry-for-ai --skill sentry-instrumentGet Sentry capturing a signal in an application — from a brand-new install (first error) to adding any later signal to a project that already has Sentry. This is the single playbook for “wire Sentry up to capture X.”
The bulk of the detail lives elsewhere: per-platform code in the Sentry docs (mapped in
references/sdk-docs.md), per-signal strategy under
references/concepts/, project provisioning
in references/new-project.md, and the confirm-it-works
loop in references/setup-verification.md.
This file is the orchestration — read the reference you need at each step, and don’t
read a reference before you need it.
Decide what you’re actually doing; it gates how much you run. When in doubt, default to first-error.
| Scope | When | What runs |
|---|---|---|
| First error | Brand-new install, no Sentry yet | Detect setup ownership, then provision and install the selected base. Verify a real error when the path supports it; disclose any trace-only limitation. Defer additional signals (logging, profiling, replay, metrics, …). |
| Add a signal | Sentry already installed; user wants one more signal | Preserve the base install, run setup-ownership detection, then wire only that signal. |
| Full setup | “Set it up properly / sensible defaults” | Run the ownership-aware base setup, then propose the rest of a baseline (releases, source maps, an uptime monitor once the app has a production URL, and any signals that fit the app) and add what the user accepts. |
Never over-instrument — wiring up logging, session replay, profiling, metrics, etc.
upfront when the user only asked to get Sentry working is doing more than they asked
for. (The base init includes tracing — that’s the SDK’s recommended default, not
over-instrumentation.)
Run setup-ownership detection for every scope, including add-a-signal:
references/first-error-setup.md.references/sdk-docs.md without reinstalling Sentry.Fetch the platform’s docs pages; inspect package manifests and existing Sentry,
OpenTelemetry, and framework instrumentation.
Before a fresh install or any AI-monitoring change, read
references/concepts/ai-monitoring.md and apply
its setup-ownership rules based on project state — not request wording.
Choose one owner for each AI runtime, preserve existing instrumentation where possible,
and never create a second Sentry initialization, OTLP exporter, or AI span producer.
For add a signal, after completing any framework-owned handoff above, preserve the selected base install and go to Step 3 for the requested signal.
For first-error and full setup, when neither framework owns setup, continue with
Steps 2 onward of first-error-setup.md: provision a project, install the SDK’s
recommended default init (errors + tracing), verify a real error, push to production,
and confirm stack traces will be readable.
Also read references/concepts/errors.md for the
baseline-signal context.
Under first-error scope you’re done after the selected setup and its verification.
Under full setup, continue from the signals the selected setup already covers:
propose the rest of a solid baseline (releases, plus any signals that fit the app) and
wire what the user accepts via Step 3. Respect the selected setup owner from the AI
monitoring ownership rules; do not add a second SDK/exporter unless the user chooses to
switch routes. If they take the stack-trace half,
references/debug-artifacts/index.md carries the
per-platform artifact upload — source maps for JS, dSYM/ProGuard/R8 for native and
mobile.
Use the platform confirmed during Step 2 and its page from
references/sdk-docs.md.
For each signal the scope calls for:
references/concepts/choosing-a-signal.md.
For a chosen signal, the matching references/concepts/<signal>.md covers strategy,
sample-rate philosophy, naming, and pitfalls — including
references/concepts/ai-monitoring.md for
the gen_ai.* model, conversation-ID rules, token/cost accounting, and the AI
sampling and PII strategy (the per-platform code then lives in that platform’s AI
monitoring docs). Skip this when the user already said “add tracing, you pick the
defaults” — go straight to the HOW.references/sdk-docs.md describes — and
apply the code.Signals this skill wires up: error monitoring, tracing/performance, profiling (requires tracing), logging, metrics, cron check-in code, session replay, user feedback, uptime monitors, and AI/LLM monitoring.
Uptime has no SDK code. Instead of fetching a docs page, read
references/concepts/uptime.md, confirm the production
URL with the user, and create the monitor with the MCP’s create_uptime_monitor.
For AI/LLM monitoring, keep input and output capture enabled by default because the Agent Tracing transcript and debugging workflow rely on prompts, responses, tool arguments, and tool results. If the user raises a privacy, security, compliance, or volume concern, follow the docs to disable or scope capture instead. Preserve any capture restrictions they have already chosen.
When naming custom span or log attributes, open only the matching domain reference below. Prefer these stable keys over invented names. Deprecated attributes are omitted.
angularappartawsbrowsercacheclientcloudcloudflarecodeculturedbdeviceerroreventexceptionfaasfileflaggcpgen_aigeneralgraphqlgrpchttpjsonrpcjvmkoaloggermcpmdcmessagingmiddlewarenavigationnelnetworkosotelparamsprocessreactremixresourcerpcscoresentryserverservicesessionstatethreadtimbertrpcuiurluseruser_agentvercelFor a fresh install the spine already verified the first error.
For an added signal, close the loop with
references/setup-verification.md: trigger the
signal by exercising the real code path that emits it, poll the MCP to confirm it
arrived, surface the direct issue URL, and confirm the stack trace is readable.
The task isn’t done until the event is seen in Sentry — don’t stop at “go check your
dashboard.”
After the first error or a new signal is confirmed, offer concrete follow-ups without auto-running them:
dataCollection options:
https://docs.sentry.io/platforms/javascript/guides/<guide>/configuration/options/#dataCollection
(for example, cloudflare for Workers and Pages, nextjs for Next.js, or node for
Node.js). Use the
JavaScript data collection options
when no platform-specific guide applies.
Keep this optional; change capture only if requested.
Do not offer this JavaScript SDK option for Python, PHP, unknown SDKs, or
framework-owned OTLP setups without a JavaScript Sentry SDK.references/concepts/uptime.md covers finding the
real URL (production events in Sentry first) and checking it before creating.init).references/debug-artifacts/index.md routes to
the artifact procedure per platform, and
references/releases/index.md routes to releases —
the release/environment tag at minimum (a one-option change worth making before
anything ships), and the CI pipeline with commits and deploys if the user wants it.
For a release feature that’s already wired but not working, sentry-setup-releases is
the diagnostic entry point.The signal’s code is in place, and a real event of that type has been confirmed in Sentry via the MCP (with the issue URL surfaced) — or, if nothing landed, the failure has been named and troubleshot rather than papered over with “check your dashboard.”