The Complete Production SOP: How to Deploy and Run Sentry Fullstack Error Monitoring & Performance Tracing in Autonomous AI Agents
Deploy sentry-fullstack-error-telemetry in Codex, Claude Code, Cursor, and Windsurf. Complete SOP with verified Next.js prompts, tracing, and sourcemap rules.
Technical Overview & Architectural Context
Autonomous coding agents frequently misconfigure fullstack telemetry. When prompted to instrument Next.js or Node.js applications with Sentry, agents routinely mix browser-side and server-side runtime imports, inject browser tokens into Edge runtimes, or configure global uncaught listeners that crash React 19 Server Components. Furthermore, agents often miss configuring `sentry.edge.config.ts`, omit release identifiers required for source map artifacts, and set `tracesSampleRate: 1.0` in high-throughput endpoints, exhaustively draining project telemetry quotas within minutes. The `sentry-fullstack-error-telemetry` skill eliminates this non-deterministic behavior by injecting strict, pre-audited procedural boundaries. It forces the autonomous agent to isolate Sentry initialization across client, server, and edge layers, establishes explicit tag-based exception capture with contextual user redaction, and mandates quota-protective sampling configurations before validating the build pipeline.
Prerequisites & Environment Requirements
Verified Search Intents & Long-Tail Queries Solved
This operational tutorial is engineered to provide deterministic solutions for these developer search queries:
Step-by-Step Execution Playbook
Local Environment Setup & SKILL.md Mounting
Create the local skill manifest directory and inject verified procedural rules into the agent runtime.
To register `sentry-fullstack-error-telemetry` across Codex, Claude Code, Cursor, or Windsurf, mount the SKILL.md definition into the agent's active configuration path. The agent parses the YAML metadata frontmatter (`triggers`, `permissions`) and references the procedural rules during execution planning without bloating the base system prompt.
mkdir -p .cursor/skills/sentry-fullstack-error-telemetry && curl -fsSL https://askills.dev/api/skills/sentry-fullstack-error-telemetry/raw -o .cursor/skills/sentry-fullstack-error-telemetry/SKILL.md---
name: "sentry-fullstack-error-telemetry"
description: "Capture uncaught exceptions, distributed trace spans, and performance anomalies with Sentry."
metadata:
author: "Sentry"
version: "1.0.0"
runtime_compatibility:
- "codex"
- "claude-code"
- "cursor"
- "windsurf"
triggers:
- "setup sentry nextjs"
- "capture exception sentry"
- "upload sourcemaps sentry"
permissions:
fs_read: true
fs_write: "workspace"
shell_exec: false
net_access: false
---
# Sentry Fullstack Error Monitoring & Performance Tracing
Configures Sentry across Next.js/Node: sentry.client.config.ts, sentry.server.config.ts, sentry.edge.config.ts, source map uploads in CI, capturing handled exceptions with captureException, and setting user context.
## Execution SOP & Rules
1. Run setup: npx @sentry/wizard@latest -i nextjs to scaffold configuration files.
2. Set user context: Sentry.setUser({ id: user.id, email: user.email }).
3. Capture handled errors: Sentry.captureException(error, { tags: { section: 'billing' } }).
4. Tune trace sample rates: tracesSampleRate: 0.1 to avoid overwhelming Sentry quotas in high-traffic apps.
## Verification Checklist
- Run local linting, syntax validation, and type-checks before reporting completion.
- Ensure all created or modified files adhere to workspace boundaries and avoid uncommitted secrets.
- Verify tests or build commands exit cleanly with return code 0.Mount skills in `.cursor/skills` or `.claude/skills` locally instead of global paths so that team members inherit identical telemetry boundaries via version control.
Ensure `fs_write` is restricted to `'workspace'`. Do not allow the agent to execute shell commands with root privileges when installing SDK wrappers.
Environment Secrets & Dependency Validation
Inject required Sentry DSNs and Auth tokens safely without leaking credentials into the LLM context window.
Autonomous agents often request or dump secret keys directly into interactive chat prompts. To comply with security score 98/100 parameters, isolate secrets in local environment files (`.env.local`) and configure `.gitignore` before triggering SDK scaffolding.
grep -q 'SENTRY_AUTH_TOKEN' .gitignore || echo -e '\n.env*.local\n.sentryclirc' >> .gitignore# Production / Staging Sentry DSN
NEXT_PUBLIC_SENTRY_DSN="https://[email protected]/0000000"
SENTRY_DSN="https://[email protected]/0000000"
SENTRY_AUTH_TOKEN="sntrys_your_masked_auth_token_here"
SENTRY_ORG="my-org"
SENTRY_PROJECT="nextjs-prod"Use `NEXT_PUBLIC_SENTRY_DSN` strictly for client-side ingest. Restrict backend DSN tokens to server-only environment variables to prevent quota hijacking.
Never instruct the agent to run `cat .env.local` to verify keys. Agents should verify variable presence using `test -n "$SENTRY_DSN"` to avoid token leakage in LLM logs.
Intent Matching & Trigger Invocation
Trigger deterministic code generation across Next.js config layers using frontmatter triggers.
Provide the agent with explicit operational triggers defined in `SKILL.md` (e.g., `setup sentry nextjs`, `capture exception sentry`). The agent matches the trigger and establishes the required modular structure: `sentry.client.config.ts`, `sentry.server.config.ts`, and `sentry.edge.config.ts`.
import * as Sentry from '@sentry/nextjs';
Sentry.init({
dsn: process.env.SENTRY_DSN || process.env.NEXT_PUBLIC_SENTRY_DSN,
tracesSampleRate: process.env.NODE_ENV === 'production' ? 0.1 : 1.0,
debug: false,
beforeSend(event) {
if (event.request?.headers) {
delete event.request.headers['authorization'];
delete event.request.headers['cookie'];
}
return event;
},
});Instruct the agent to include a `beforeSend` sanitization hook in server and edge configs to automatically purge PII and authorization headers before transmission.
Avoid importing `@sentry/nextjs` in components marked `'use client'` without referencing client config; use the specific client build to prevent SSR tree-shaking failures.
Verification, Linting & Output Quality Gate
Execute automated self-healing checks and build validation before accepting agent telemetry deliverables.
The skill mandates that the agent execute local validation scripts prior to marking the task complete. The agent must verify that Next.js wraps the configuration correctly via `withSentryConfig` in `next.config.mjs` and that TypeScript compiler passes without errors.
pnpm tsc --noEmit && pnpm next build --dry-runimport { withSentryConfig } from '@sentry/nextjs';
/** @type {import('next').NextConfig} */
const nextConfig = {
reactStrictMode: true,
};
export default withSentryConfig(nextConfig, {
org: process.env.SENTRY_ORG,
project: process.env.SENTRY_PROJECT,
silent: !process.env.CI,
widenClientFileUpload: true,
hideSourceMaps: true,
disableLogger: true,
});Always verify that `hideSourceMaps: true` is present so production source maps are uploaded to Sentry and stripped from the public `.next/static` distribution bundle.
If using Next.js Turbopack (`next dev --turbo`), ensure your agent does not inject Webpack-specific Sentry plugins that break the development build pipeline.
Real-World Scenario: Instrumenting High-Throughput Checkout API with Contextual Error Handling and Tracing
“setup sentry nextjs in our checkout workflow. Capture exception sentry whenever the Stripe webhook validation fails or a card payment is declined, attach user metadata, tag the error with section 'checkout-billing', and set trace sample rate to 0.1.”
Runtime Troubleshooting & Failure Modes
Root Cause: The agent attempted to import Node-specific Sentry APIs inside an Edge Runtime route segment (`export const runtime = 'edge'`).
Ensure edge route files only import from '@sentry/nextjs' using the Edge-compatible entry points and verify `sentry.edge.config.ts` is initialized: `import * as Sentry from '@sentry/nextjs';` and avoid referencing Node core modules (fs, path) in scopes called by the Edge runtime.Root Cause: The agent attempted to run sourcemap artifact upload without `SENTRY_AUTH_TOKEN` exported or provided a malformed token inside `.sentryclirc`.
Run `export SENTRY_AUTH_TOKEN="<valid_token>"` in your shell environment and instruct the agent: `upload sourcemaps sentry using existing environment variables without writing tokens to disk`.Frequently Asked Questions (Sentry Fullstack Error Monitoring & Performance Tracing SOP)
Q:Can I use Sentry Fullstack Error Monitoring & Performance Tracing across Codex, Claude Code, and Cursor simultaneously?
Yes. The skill conforms to the universal SKILL.md specification supported across all modern agent runtimes. By placing the file in your repository's `.cursor/skills/`, `.claude/skills/`, or root `.agents/skills/` directory, any compliant autonomous runtime will identify the triggers and enforce the exact same operational SOP.
Q:How does Sentry Fullstack Error Monitoring & Performance Tracing prevent context window overflow during long agent sessions?
By establishing concise procedural boundaries and deterministic validation gates rather than polluting system prompts with redundant rules. The SKILL.md limits runtime metadata to actionable rules (configuration separation, sampling rate enforcement, sourcemap stripping), consuming less than 400 prompt tokens while eliminating hallucinated SDK APIs.
Q:Does this skill require escalated root or container permissions?
No. It is audited with a security score of 98/100 and runs safely within workspace-scoped sandboxes. The skill explicitly sets `shell_exec: false` and `net_access: false` in its permissions contract, ensuring the agent only modifies authorized workspace configuration files without accessing external networks or arbitrary host processes.
Ready to equip your autonomous agent with Sentry Fullstack Error Monitoring & Performance Tracing?
Copy the complete audited SKILL.md specification or download the 1-click zip bundle directly from our verified registry.