[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M795QWXR3FR3DXYTNTB77CCE":3,"skill-same:01M795QWXR3FR3DXYTNTB77CCE":59},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":36,"commitSha":37,"skillDirectory":38,"forksCount":39,"repositoryHtmlUrl":40,"repositoryHomepageUrl":6,"ownerHtmlUrl":41,"ownerBlogUrl":42,"ownerDescription":43,"updatedAt":44,"install":45,"resources":58},"01M795QWXR3FR3DXYTNTB77CCE","sentry-prod-checklist",null,"Production deployment checklist for Sentry integration.\nUse when preparing a production deployment, auditing an existing\nSentry setup, or running a go-live readiness review.\nTrigger: \"sentry production checklist\", \"deploy sentry\",\n\"sentry go-live\", \"audit sentry config\", \"production readiness sentry\".","jukeyman\u002Fjukeyman-skills","jukeyman","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F142960420?v=4","01M78FR4Y3DHMMCBCC0GXXNB3F","RICK JEFFERSON","01M78FR4Z8RVQRAD31Y5J7V6EB",1,"MIT","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsaas-packs--sentry-pack--sentry-prod-checklist\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: sentry-prod-checklist\ndescription: |\n  Production deployment checklist for Sentry integration.\n  Use when preparing a production deployment, auditing an existing\n  Sentry setup, or running a go-live readiness review.\n  Trigger: \"sentry production checklist\", \"deploy sentry\",\n  \"sentry go-live\", \"audit sentry config\", \"production readiness sentry\".\nallowed-tools: Read, Grep, Glob, Bash(npm:*), Bash(npx:*), Bash(node:*), Bash(curl:*), Bash(sentry-cli:*)\nversion: 1.0.0\nlicense: MIT\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\ncompatible-with: claude-code, codex, openclaw\ntags: [saas, sentry, deployment, production, checklist, operations]\n---\n# Sentry Production Deployment Checklist\n\n## Overview\n\nWalk through every production-critical Sentry configuration item before a deploy — SDK init options, source map uploads, alert routing, PII scrubbing, sample rate tuning, and test error verification. Covers `@sentry\u002Fnode` (v8+) and `sentry-cli` workflows.\n\n**Use when:**\n- Preparing a first production deploy with Sentry\n- Auditing an existing Sentry config after an incident\n- Running a go-live readiness review\n- Onboarding a new service into Sentry monitoring\n\n## Prerequisites\n\n- `@sentry\u002Fnode` (or framework-specific SDK like `@sentry\u002Fnextjs`, `@sentry\u002Freact`) installed\n- Sentry project created with a **dedicated production DSN** (separate from dev\u002Fstaging)\n- `sentry-cli` installed globally or as a devDependency (`npm i -D @sentry\u002Fcli`)\n- `SENTRY_AUTH_TOKEN` with scope `project:releases` available in CI environment\n- Build pipeline that produces source maps\n\n## Instructions\n\nWork through each section in order. Check off each item as you verify it.\n\n### Step 1 — DSN and Environment Variables\n\n- [ ] **DSN set via environment variable, not hardcoded in source code**\n\n```typescript\n\u002F\u002F CORRECT — DSN from environment\nSentry.init({\n  dsn: process.env.SENTRY_DSN,\n});\n\n\u002F\u002F WRONG — hardcoded DSN leaks project ID and org info\nSentry.init({\n  dsn: 'https:\u002F\u002Fabc123@o456.ingest.sentry.io\u002F789',\n});\n```\n\nVerify with: `grep -r \"ingest.sentry.io\" src\u002F --include=\"*.ts\" --include=\"*.js\"` — should return zero results.\n\n- [ ] **`SENTRY_DSN` set in production environment** (not just `.env.local`)\n- [ ] **`SENTRY_ORG` and `SENTRY_PROJECT` set for CLI operations**\n\n### Step 2 — Environment Tag\n\n- [ ] **`environment` tag set to `'production'`**\n\n```typescript\nSentry.init({\n  dsn: process.env.SENTRY_DSN,\n  environment: process.env.NODE_ENV || 'production',\n});\n```\n\nThis enables environment-scoped alert rules and release health filtering. Without it, all events land in the default (empty) environment.\n\n### Step 3 — Release Tracking\n\n- [ ] **`release` set to match the deploy version**\n\n```typescript\nSentry.init({\n  dsn: process.env.SENTRY_DSN,\n  environment: 'production',\n  release: process.env.SENTRY_RELEASE || `myapp@${process.env.npm_package_version}`,\n});\n```\n\nThe release value must match exactly what you pass to `sentry-cli releases new`. Mismatches break source map resolution and release health tracking.\n\n### Step 4 — Error Sample Rate\n\n- [ ] **`sampleRate` tuned — not 1.0 in high-traffic production**\n\n```typescript\nSentry.init({\n  \u002F\u002F For most apps: 0.1 to 0.25 captures enough to spot trends\n  \u002F\u002F without burning through your event quota\n  sampleRate: 0.25, \u002F\u002F 25% of errors captured\n\n  \u002F\u002F For low-traffic apps or critical services, 1.0 is fine\n  \u002F\u002F sampleRate: 1.0,\n});\n```\n\n| Traffic level | Recommended `sampleRate` |\n|---------------|--------------------------|\n| \u003C 10K errors\u002Fday | 1.0 |\n| 10K-100K errors\u002Fday | 0.25 |\n| > 100K errors\u002Fday | 0.1 |\n\n### Step 5 — Traces Sample Rate\n\n- [ ] **`tracesSampleRate` tuned (0.05-0.2 for production)**\n\n```typescript\nSentry.init({\n  tracesSampleRate: 0.1, \u002F\u002F 10% of transactions traced\n\n  \u002F\u002F Or use tracesSampler for endpoint-specific rates\n  tracesSampler: (samplingContext) => {\n    const name = samplingContext.transactionContext?.name || '';\n\n    \u002F\u002F Never trace health checks\n    if (name.includes('\u002Fhealth') || name.includes('\u002Fready')) return 0;\n\n    \u002F\u002F Always trace payments\n    if (name.includes('\u002Fcheckout') || name.includes('\u002Fpayment')) return 1.0;\n\n    \u002F\u002F Default: 10%\n    return 0.1;\n  },\n});\n```\n\nNever ship `tracesSampleRate: 1.0` in production — it generates massive event volume and will exhaust your quota within hours on any real workload.\n\n### Step 6 — Source Map Upload\n\n- [ ] **Source maps uploaded via `sentry-cli releases files`**\n\n```bash\n#!\u002Fbin\u002Fbash\n# Run in CI after build, before deploy\nset -euo pipefail\n\nVERSION=\"${SENTRY_RELEASE:-$(git rev-parse --short HEAD)}\"\n\n# Create the release\nsentry-cli releases new \"$VERSION\"\n\n# Associate commits for suspect commits feature\nsentry-cli releases set-commits \"$VERSION\" --auto\n\n# Upload source maps from build output\nsentry-cli releases files \"$VERSION\" upload-sourcemaps .\u002Fdist \\\n  --url-prefix '~\u002Fstatic\u002Fjs' \\\n  --validate\n\n# Mark release as deployed\nsentry-cli releases finalize \"$VERSION\"\nsentry-cli releases deploys \"$VERSION\" new -e production\n```\n\n- [ ] `--url-prefix` matches the path where assets are served (e.g., `~\u002Fstatic\u002Fjs` or `~\u002Fassets`)\n- [ ] `--validate` flag is used to catch malformed maps at build time\n- [ ] Source maps are NOT served to browsers (add to `.gitignore` or strip from deploy artifact)\n\nVerify upload succeeded:\n```bash\nsentry-cli releases files \"$VERSION\" list\n# Should show .js and .js.map files with correct paths\n```\n\n### Step 7 — `beforeSend` Noise Filter\n\n- [ ] **`beforeSend` configured to drop noise**\n\n```typescript\nSentry.init({\n  beforeSend(event, hint) {\n    const error = hint?.originalException;\n    const message = typeof error === 'string' ? error : error?.message || '';\n\n    \u002F\u002F Drop browser noise that is never actionable\n    const noise = [\n      'ResizeObserver loop',\n      'Non-Error promise rejection captured',\n      \u002FLoading chunk \\d+ failed\u002F,\n      'Network request failed',\n      'AbortError',\n      'TypeError: cancelled',\n      'TypeError: Failed to fetch',\n    ];\n\n    for (const pattern of noise) {\n      if (pattern instanceof RegExp ? pattern.test(message) : message.includes(pattern)) {\n        return null; \u002F\u002F Drop this event\n      }\n    }\n\n    \u002F\u002F Scrub auth headers if they leak into request context\n    if (event.request?.headers) {\n      delete event.request.headers['Authorization'];\n      delete event.request.headers['Cookie'];\n      delete event.request.headers['X-API-Key'];\n    }\n\n    return event;\n  },\n});\n```\n\n### Step 8 — PII Scrubbing\n\n- [ ] **PII scrubbing enabled: `sendDefaultPii: false`**\n\n```typescript\nSentry.init({\n  sendDefaultPii: false, \u002F\u002F Do NOT send cookies, user IPs, or auth headers\n\n  \u002F\u002F If you need user context, set it explicitly with scrubbed data\n  \u002F\u002F Sentry.setUser({ id: user.id }); \u002F\u002F ID only, no email\u002Fname\n});\n```\n\nAlso verify in Sentry project settings:\n- **Settings > Security & Privacy > Data Scrubbing** is enabled\n- **IP Address** collection is disabled if not needed\n- **Sensitive Fields** list includes your app-specific fields (e.g., `ssn`, `creditCard`)\n\n### Step 9 — Alert Rules\n\n- [ ] **Alert rules configured for production environment**\n\nSet up these minimum alert rules in **Alerts > Create Alert Rule**:\n\n| Alert | Type | Condition | Action |\n|-------|------|-----------|--------|\n| New issue in production | Issue | First seen, `environment:production` | Slack channel + email |\n| Regression detected | Issue | Regressed, `environment:production` | Slack channel |\n| Error spike | Metric | Error count > N in 5 min | PagerDuty (on-call) |\n| P95 latency breach | Metric | `p95(transaction.duration)` > threshold | Slack #performance |\n| Crash-free rate drop | Release health | Crash-free sessions \u003C 99% | Email + Slack |\n\n- [ ] Alert actions route to correct channels (not a dead channel)\n- [ ] PagerDuty \u002F OpsGenie integration tested with a test alert\n\n### Step 10 — Process Exit Flush (Serverless \u002F CLI)\n\n- [ ] **`Sentry.flush()` called before process exit**\n\nFor serverless functions, CLI tools, or any short-lived process, events may be lost if the process exits before the SDK flushes its queue:\n\n```typescript\n\u002F\u002F AWS Lambda \u002F serverless\nimport * as Sentry from '@sentry\u002Fnode';\n\nexport const handler = Sentry.wrapHandler(async (event) => {\n  \u002F\u002F Your handler logic\n  return { statusCode: 200 };\n});\n\n\u002F\u002F CLI tool \u002F script\nasync function main() {\n  try {\n    await doWork();\n  } catch (err) {\n    Sentry.captureException(err);\n    await Sentry.flush(2000); \u002F\u002F 2000ms timeout — enough for network round-trip\n    process.exit(1);\n  }\n}\n```\n\nFor long-running servers (Express, Fastify), this is handled automatically — skip this step.\n\n### Step 11 — Test Error Verification\n\n- [ ] **Test error sent and verified in Sentry dashboard**\n\n```typescript\n\u002F\u002F Send a test error after deploy\nSentry.captureException(new Error('Production deploy verification — safe to ignore'));\n\n\u002F\u002F Or from CLI\n\u002F\u002F node -e \"\n\u002F\u002F   const Sentry = require('@sentry\u002Fnode');\n\u002F\u002F   Sentry.init({ dsn: process.env.SENTRY_DSN, environment: 'production' });\n\u002F\u002F   Sentry.captureMessage('Deploy verification test');\n\u002F\u002F   Sentry.flush(2000).then(() => console.log('Test event sent')); \u002F\u002F 2s flush timeout\n\u002F\u002F \"\n```\n\nAfter sending, verify in the Sentry dashboard:\n1. Event appears in **Issues** with correct `environment:production`\n2. Stack trace shows **original source** (not minified) — confirms source maps work\n3. Release tag matches your deployed version\n4. No PII (cookies, IPs, auth headers) in the event payload\n\n### Step 12 — Inbound Filters\n\n- [ ] **Inbound filters enabled for known browser noise**\n\nIn Sentry dashboard under **Settings > Inbound Filters**, enable:\n\n- **Filter out known web crawlers** (Googlebot, Bingbot generate noise)\n- **Filter out legacy browsers** (IE 10 and below)\n- **Filter out localhost events** (stray dev events)\n- **Custom inbound filters** for domains you don't control\n\nThese filters drop events server-side before they count against your quota, unlike `beforeSend` which drops client-side after the network request.\n\n### Verification Script\n\nRun this after completing all checklist items:\n\n```bash\n#!\u002Fbin\u002Fbash\n# scripts\u002Fverify-sentry-prod.sh\nset -euo pipefail\n\necho \"=== Sentry Production Verification ===\"\n\nPASS=0; FAIL=0\n\ncheck() {\n  if eval \"$2\" > \u002Fdev\u002Fnull 2>&1; then\n    echo \"  PASS: $1\"; ((PASS++))\n  else\n    echo \"  FAIL: $1\"; ((FAIL++))\n  fi\n}\n\n# Environment variables\nfor var in SENTRY_DSN SENTRY_ORG SENTRY_PROJECT SENTRY_AUTH_TOKEN; do\n  check \"$var is set\" \"[ -n \\\"\\${$var:-}\\\" ]\"\ndone\n\n# CLI authentication\ncheck \"sentry-cli authenticated\" \"sentry-cli info\"\n\n# Source maps uploaded\nRELEASE=\"${SENTRY_RELEASE:-$(git rev-parse --short HEAD)}\"\ncheck \"Source maps for $RELEASE\" \\\n  \"[ \\$(sentry-cli releases files \\\"$RELEASE\\\" list 2>\u002Fdev\u002Fnull | wc -l) -gt 1 ]\"\n\n# Network connectivity\ncheck \"sentry.io reachable\" \\\n  \"[ \\$(curl -s -o \u002Fdev\u002Fnull -w '%{http_code}' https:\u002F\u002Fsentry.io\u002Fapi\u002F0\u002F) = '200' ]\"\n\n# No hardcoded DSN in source\ncheck \"No hardcoded DSN in src\u002F\" \\\n  \"! grep -r 'ingest.sentry.io' src\u002F --include='*.ts' --include='*.js' --include='*.tsx' 2>\u002Fdev\u002Fnull | grep -v node_modules\"\n\necho \"\"\necho \"=== Results: $PASS passed, $FAIL failed ===\"\n[ \"$FAIL\" -eq 0 ] && echo \"All checks passed.\" || exit 1\n```\n\n## Output\n\nAfter completing this checklist, you will have:\n- Production-hardened `Sentry.init()` with tuned sample rates and PII scrubbing\n- Source maps uploaded and validated via `sentry-cli` for the current release\n- `beforeSend` filtering known browser noise before it burns quota\n- Alert rules routing to Slack, email, and PagerDuty for the production environment\n- A verified test error visible in the dashboard with readable stack traces\n- Inbound filters blocking crawler and legacy browser noise server-side\n\n## Error Handling\n\n| Error | Cause | Solution |\n|-------|-------|----------|\n| Stack traces show minified code | Source maps missing or `--url-prefix` wrong | Re-upload with correct prefix; run `sentry-cli sourcemaps explain` to diagnose |\n| Events not appearing in dashboard | Wrong DSN or network blocked | Verify `SENTRY_DSN` is the production DSN; check firewall allows `*.ingest.sentry.io` on HTTPS |\n| `release` mismatch warning | SDK release differs from CLI release | Ensure `Sentry.init({ release })` matches `sentry-cli releases new $VERSION` exactly |\n| Events from wrong environment | `environment` not set in SDK init | Explicitly set `environment: 'production'` — do not rely on defaults |\n| Excessive event volume \u002F quota exhausted | `sampleRate: 1.0` on high-traffic service | Lower to 0.1-0.25; add `beforeSend` filters; enable server-side inbound filters |\n| Alerts not firing | Alert rules scoped to wrong environment | Edit alert: filter to `environment:production`; test with `Sentry.captureMessage()` |\n| Events lost in serverless \u002F CLI | Process exits before flush | Call `await Sentry.flush(2000)` before `process.exit()` or use `Sentry.wrapHandler()` |\n| `beforeSend` dropping real errors | Overly broad noise filter | Audit filter patterns; log dropped events to a secondary sink during rollout |\n\n## Examples\n\n**Example 1: Full production init (Node.js \u002F Express)**\n\n```typescript\nimport * as Sentry from '@sentry\u002Fnode';\n\nSentry.init({\n  dsn: process.env.SENTRY_DSN,\n  environment: 'production',\n  release: process.env.SENTRY_RELEASE,\n  debug: false,\n  sendDefaultPii: false,\n  sampleRate: 0.25,\n  tracesSampleRate: 0.1,\n  maxBreadcrumbs: 50,\n  attachStacktrace: true,\n\n  ignoreErrors: [\n    'ResizeObserver loop',\n    'Non-Error promise rejection captured',\n    \u002FLoading chunk \\d+ failed\u002F,\n  ],\n\n  beforeSend(event, hint) {\n    if (event.request?.headers) {\n      delete event.request.headers['Authorization'];\n      delete event.request.headers['Cookie'];\n    }\n    return event;\n  },\n\n  tracesSampler: (ctx) => {\n    const name = ctx.transactionContext?.name || '';\n    if (name.includes('\u002Fhealth')) return 0;\n    if (name.includes('\u002Fpayment')) return 1.0;\n    return 0.1;\n  },\n});\n```\n\n**Example 2: CI source map upload (GitHub Actions)**\n\n```yaml\n# .github\u002Fworkflows\u002Fdeploy.yml\n- name: Upload source maps to Sentry\n  env:\n    SENTRY_AUTH_TOKEN: ${{ secrets.SENTRY_AUTH_TOKEN }}\n    SENTRY_ORG: my-org\n    SENTRY_PROJECT: my-project\n    VERSION: ${{ github.sha }}\n  run: |\n    npx sentry-cli releases new \"$VERSION\"\n    npx sentry-cli releases set-commits \"$VERSION\" --auto\n    npx sentry-cli releases files \"$VERSION\" upload-sourcemaps .\u002Fdist \\\n      --url-prefix '~\u002Fstatic\u002Fjs' --validate\n    npx sentry-cli releases finalize \"$VERSION\"\n    npx sentry-cli releases deploys \"$VERSION\" new -e production\n```\n\n**Example 3: Serverless flush pattern (AWS Lambda)**\n\n```typescript\nimport * as Sentry from '@sentry\u002Fnode';\n\nSentry.init({\n  dsn: process.env.SENTRY_DSN,\n  environment: 'production',\n  release: process.env.SENTRY_RELEASE,\n  tracesSampleRate: 0.2,\n});\n\nexport const handler = Sentry.wrapHandler(async (event, context) => {\n  \u002F\u002F wrapHandler automatically calls flush() on completion\n  const result = await processEvent(event);\n  return { statusCode: 200, body: JSON.stringify(result) };\n});\n```\n\n## Resources\n\n- [Sentry Configuration Options](https:\u002F\u002Fdocs.sentry.io\u002Fplatforms\u002Fjavascript\u002Fconfiguration\u002Foptions\u002F) — full SDK init reference\n- [Source Maps Upload](https:\u002F\u002Fdocs.sentry.io\u002Fplatforms\u002Fjavascript\u002Fsourcemaps\u002F) — bundler plugins and CLI upload\n- [sentry-cli releases](https:\u002F\u002Fdocs.sentry.io\u002Fcli\u002Freleases\u002F) — `new`, `set-commits`, `finalize`, `deploys`\n- [Alert Rules](https:\u002F\u002Fdocs.sentry.io\u002Fproduct\u002Falerts\u002F) — issue alerts, metric alerts, uptime monitors\n- [Release Health](https:\u002F\u002Fdocs.sentry.io\u002Fproduct\u002Freleases\u002Fhealth\u002F) — crash-free rates and session tracking\n- [Data Scrubbing](https:\u002F\u002Fdocs.sentry.io\u002Fsecurity-legal-pii\u002Fscrubbing\u002F) — server-side PII removal\n- [Inbound Filters](https:\u002F\u002Fdocs.sentry.io\u002Fproduct\u002Fdata-management-settings\u002Ffiltering\u002F) — server-side event filtering\n\n## Next Steps\n\nAfter completing this production checklist:\n1. **Set up release health monitoring** — track crash-free session rates across releases\n2. **Configure ownership rules** — route issues to the right team based on file paths or error tags\n3. **Add custom dashboards** — build a deployment dashboard showing error rates, P95 latency, and throughput per release\n4. **Schedule quarterly audits** — re-run this checklist after major dependency upgrades or architecture changes\n5. **Enable Session Replay** (if using `@sentry\u002Fbrowser`) — capture user sessions for faster debugging\n","# Sentry Production Deployment Checklist\n\n## Overview\n\nWalk through every production-critical Sentry configuration item before a deploy — SDK init options, source map uploads, alert routing, PII scrubbing, sample rate tuning, and test error verification. Covers `@sentry\u002Fnode` (v8+) and `sentry-cli` workflows.\n\n**Use when:**\n- Preparing a first production deploy with Sentry\n- Auditing an existing Sentry config after an incident\n- Running a go-live readiness review\n- Onboarding a new service into Sentry monitoring\n\n## Prerequisites\n\n- `@sentry\u002Fnode` (or framework-specific SDK like `@sentry\u002Fnextjs`, `@sentry\u002Freact`) installed\n- Sentry project created with a **dedicated production DSN** (separate from dev\u002Fstaging)\n- `sentry-cli` installed globally or as a devDependency (`npm i -D @sentry\u002Fcli`)\n- `SENTRY_AUTH_TOKEN` with scope `project:releases` available in CI environment\n- Build pipeline that produces source maps\n\n## Instructions\n\nWork through each section in order. Check off each item as you verify it.\n\n### Step 1 — DSN and Environment Variables\n\n- [ ] **DSN set via environment variable, not hardcoded in source code**\n\n```typescript\n\u002F\u002F CORRECT — DSN from environment\nSentry.init({\n  dsn: process.env.SENTRY_DSN,\n});\n\n\u002F\u002F WRONG — hardcoded DSN leaks project ID and org info\nSentry.init({\n  dsn: 'https:\u002F\u002Fabc123@o456.ingest.sentry.io\u002F789',\n});\n```\n\nVerify with: `grep -r \"ingest.sentry.io\" src\u002F --include=\"*.ts\" --include=\"*.js\"` — should return zero results.\n\n- [ ] **`SENTRY_DSN` set in production environment** (not just `.env.local`)\n- [ ] **`SENTRY_ORG` and `SENTRY_PROJECT` set for CLI operations**\n\n### Step 2 — Environment Tag\n\n- [ ] **`environment` tag set to `'production'`**\n\n```typescript\nSentry.init({\n  dsn: process.env.SENTRY_DSN,\n  environment: process.env.NODE_ENV || 'production',\n});\n```\n\nThis enables environment-scoped alert rules and release health filtering. Without it, all events land in the default (empty) environment.\n\n### Step 3 — Release Tracking\n\n- [ ] **`release` set to match the deploy version**\n\n```typescript\nSentry.init({\n  dsn: process.env.SENTRY_DSN,\n  environment: 'production',\n  release: process.env.SENTRY_RELEASE || `myapp@${process.env.npm_package_version}`,\n});\n```\n\nThe release value must match exactly what you pass to `sentry-cli releases new`. Mismatches break source map resolution and release health tracking.\n\n### Step 4 — Error Sample Rate\n\n- [ ] **`sampleRate` tuned — not 1.0 in high-traffic production**\n\n```typescript\nSentry.init({\n  \u002F\u002F For most apps: 0.1 to 0.25 captures enough to spot trends\n  \u002F\u002F without burning through your event quota\n  sampleRate: 0.25, \u002F\u002F 25% of errors captured\n\n  \u002F\u002F For low-traffic apps or critical services, 1.0 is fine\n  \u002F\u002F sampleRate: 1.0,\n});\n```\n\n| Traffic level | Recommended `sampleRate` |\n|---------------|--------------------------|\n| \u003C 10K errors\u002Fday | 1.0 |\n| 10K-100K errors\u002Fday | 0.25 |\n| > 100K errors\u002Fday | 0.1 |\n\n### Step 5 — Traces Sample Rate\n\n- [ ] **`tracesSampleRate` tuned (0.05-0.2 for production)**\n\n```typescript\nSentry.init({\n  tracesSampleRate: 0.1, \u002F\u002F 10% of transactions traced\n\n  \u002F\u002F Or use tracesSampler for endpoint-specific rates\n  tracesSampler: (samplingContext) => {\n    const name = samplingContext.transactionContext?.name || '';\n\n    \u002F\u002F Never trace health checks\n    if (name.includes('\u002Fhealth') || name.includes('\u002Fready')) return 0;\n\n    \u002F\u002F Always trace payments\n    if (name.includes('\u002Fcheckout') || name.includes('\u002Fpayment')) return 1.0;\n\n    \u002F\u002F Default: 10%\n    return 0.1;\n  },\n});\n```\n\nNever ship `tracesSampleRate: 1.0` in production — it generates massive event volume and will exhaust your quota within hours on any real workload.\n\n### Step 6 — Source Map Upload\n\n- [ ] **Source maps uploaded via `sentry-cli releases files`**\n\n```bash\n#!\u002Fbin\u002Fbash\n# Run in CI after build, before deploy\nset -euo pipefail\n\nVERSION=\"${SENTRY_RELEASE:-$(git rev-parse --short HEAD)}\"\n\n# Create the release\nsentry-cli releases new \"$VERSION\"\n\n# Associate commits for suspect commits feature\nsentry-cli releases set-commits \"$VERSION\" --auto\n\n# Upload source maps from build output\nsentry-cli releases files \"$VERSION\" upload-sourcemaps .\u002Fdist \\\n  --url-prefix '~\u002Fstatic\u002Fjs' \\\n  --validate\n\n# Mark release as deployed\nsentry-cli releases finalize \"$VERSION\"\nsentry-cli releases deploys \"$VERSION\" new -e production\n```\n\n- [ ] `--url-prefix` matches the path where assets are served (e.g., `~\u002Fstatic\u002Fjs` or `~\u002Fassets`)\n- [ ] `--validate` flag is used to catch malformed maps at build time\n- [ ] Source maps are NOT served to browsers (add to `.gitignore` or strip from deploy artifact)\n\nVerify upload succeeded:\n```bash\nsentry-cli releases files \"$VERSION\" list\n# Should show .js and .js.map files with correct paths\n```\n\n### Step 7 — `beforeSend` Noise Filter\n\n- [ ] **`beforeSend` configured to drop noise**\n\n```typescript\nSentry.init({\n  beforeSend(event, hint) {\n    const error = hint?.originalException;\n    const message = typeof error === 'string' ? error : error?.message || '';\n\n    \u002F\u002F Drop browser noise that is never actionable\n    const noise = [\n      'ResizeObserver loop',\n      'Non-Error promise rejection captured',\n      \u002FLoading chunk \\d+ failed\u002F,\n      'Network request failed',\n      'AbortError',\n      'TypeError: cancelled',\n      'TypeError: Failed to fetch',\n    ];\n\n    for (const pattern of noise) {\n      if (pattern instanceof RegExp ? pattern.test(message) : message.includes(pattern)) {\n        return null; \u002F\u002F Drop this event\n      }\n    }\n\n    \u002F\u002F Scrub auth headers if they leak into request context\n    if (event.request?.headers) {\n      delete event.request.headers['Authorization'];\n      delete event.request.headers['Cookie'];\n      delete event.request.headers['X-API-Key'];\n    }\n\n    return event;\n  },\n});\n```\n\n### Step 8 — PII Scrubbing\n\n- [ ] **PII scrubbing enabled: `sendDefaultPii: false`**\n\n```typescript\nSentry.init({\n  sendDefaultPii: false, \u002F\u002F Do NOT send cookies, user IPs, or auth headers\n\n  \u002F\u002F If you need user context, set it explicitly with scrubbed data\n  \u002F\u002F Sentry.setUser({ id: user.id }); \u002F\u002F ID only, no email\u002Fname\n});\n```\n\nAlso verify in Sentry project settings:\n- **Settings > Security & Privacy > Data Scrubbing** is enabled\n- **IP Address** collection is disabled if not needed\n- **Sensitive Fields** list includes your app-specific fields (e.g., `ssn`, `creditCard`)\n\n### Step 9 — Alert Rules\n\n- [ ] **Alert rules configured for production environment**\n\nSet up these minimum alert rules in **Alerts > Create Alert Rule**:\n\n| Alert | Type | Condition | Action |\n|-------|------|-----------|--------|\n| New issue in production | Issue | First seen, `environment:production` | Slack channel + email |\n| Regression detected | Issue | Regressed, `environment:production` | Slack channel |\n| Error spike | Metric | Error count > N in 5 min | PagerDuty (on-call) |\n| P95 latency breach | Metric | `p95(transaction.duration)` > threshold | Slack #performance |\n| Crash-free rate drop | Release health | Crash-free sessions \u003C 99% | Email + Slack |\n\n- [ ] Alert actions route to correct channels (not a dead channel)\n- [ ] PagerDuty \u002F OpsGenie integration tested with a test alert\n\n### Step 10 — Process Exit Flush (Serverless \u002F CLI)\n\n- [ ] **`Sentry.flush()` called before process exit**\n\nFor serverless functions, CLI tools, or any short-lived process, events may be lost if the process exits before the SDK flushes its queue:\n\n```typescript\n\u002F\u002F AWS Lambda \u002F serverless\nimport * as Sentry from '@sentry\u002Fnode';\n\nexport const handler = Sentry.wrapHandler(async (event) => {\n  \u002F\u002F Your handler logic\n  return { statusCode: 200 };\n});\n\n\u002F\u002F CLI tool \u002F script\nasync function main() {\n  try {\n    await doWork();\n  } catch (err) {\n    Sentry.captureException(err);\n    await Sentry.flush(2000); \u002F\u002F 2000ms timeout — enough for network round-trip\n    process.exit(1);\n  }\n}\n```\n\nFor long-running servers (Express, Fastify), this is handled automatically — skip this step.\n\n### Step 11 — Test Error Verification\n\n- [ ] **Test error sent and verified in Sentry dashboard**\n\n```typescript\n\u002F\u002F Send a test error after deploy\nSentry.captureException(new Error('Production deploy verification — safe to ignore'));\n\n\u002F\u002F Or from CLI\n\u002F\u002F node -e \"\n\u002F\u002F   const Sentry = require('@sentry\u002Fnode');\n\u002F\u002F   Sentry.init({ dsn: process.env.SENTRY_DSN, environment: 'production' });\n\u002F\u002F   Sentry.captureMessage('Deploy verification test');\n\u002F\u002F   Sentry.flush(2000).then(() => console.log('Test event sent')); \u002F\u002F 2s flush timeout\n\u002F\u002F \"\n```\n\nAfter sending, verify in the Sentry dashboard:\n1. Event appears in **Issues** with correct `environment:production`\n2. Stack trace shows **original source** (not minified) — confirms source maps work\n3. Release tag matches your deployed version\n4. No PII (cookies, IPs, auth headers) in the event payload\n\n### Step 12 — Inbound Filters\n\n- [ ] **Inbound filters enabled for known browser noise**\n\nIn Sentry dashboard under **Settings > Inbound Filters**, enable:\n\n- **Filter out known web crawlers** (Googlebot, Bingbot generate noise)\n- **Filter out legacy browsers** (IE 10 and below)\n- **Filter out localhost events** (stray dev events)\n- **Custom inbound filters** for domains you don't control\n\nThese filters drop events server-side before they count against your quota, unlike `beforeSend` which drops client-side after the network request.\n\n### Verification Script\n\nRun this after completing all checklist items:\n\n```bash\n#!\u002Fbin\u002Fbash\n# scripts\u002Fverify-sentry-prod.sh\nset -euo pipefail\n\necho \"=== Sentry Production Verification ===\"\n\nPASS=0; FAIL=0\n\ncheck() {\n  if eval \"$2\" > \u002Fdev\u002Fnull 2>&1; then\n    echo \"  PASS: $1\"; ((PASS++))\n  else\n    echo \"  FAIL: $1\"; ((FAIL++))\n  fi\n}\n\n# Environment variables\nfor var in SENTRY_DSN SENTRY_ORG SENTRY_PROJECT SENTRY_AUTH_TOKEN; do\n  check \"$var is set\" \"[ -n \\\"\\${$var:-}\\\" ]\"\ndone\n\n# CLI authentication\ncheck \"sentry-cli authenticated\" \"sentry-cli info\"\n\n# Source maps uploaded\nRELEASE=\"${SENTRY_RELEASE:-$(git rev-parse --short HEAD)}\"\ncheck \"Source maps for $RELEASE\" \\\n  \"[ \\$(sentry-cli releases files \\\"$RELEASE\\\" list 2>\u002Fdev\u002Fnull | wc -l) -gt 1 ]\"\n\n# Network connectivity\ncheck \"sentry.io reachable\" \\\n  \"[ \\$(curl -s -o \u002Fdev\u002Fnull -w '%{http_code}' https:\u002F\u002Fsentry.io\u002Fapi\u002F0\u002F) = '200' ]\"\n\n# No hardcoded DSN in source\ncheck \"No hardcoded DSN in src\u002F\" \\\n  \"! grep -r 'ingest.sentry.io' src\u002F --include='*.ts' --include='*.js' --include='*.tsx' 2>\u002Fdev\u002Fnull | grep -v node_modules\"\n\necho \"\"\necho \"=== Results: $PASS passed, $FAIL failed ===\"\n[ \"$FAIL\" -eq 0 ] && echo \"All checks passed.\" || exit 1\n```\n\n## Output\n\nAfter completing this checklist, you will have:\n- Production-hardened `Sentry.init()` with tuned sample rates and PII scrubbing\n- Source maps uploaded and validated via `sentry-cli` for the current release\n- `beforeSend` filtering known browser noise before it burns quota\n- Alert rules routing to Slack, email, and PagerDuty for the production environment\n- A verified test error visible in the dashboard with readable stack traces\n- Inbound filters blocking crawler and legacy browser noise server-side\n\n## Error Handling\n\n| Error | Cause | Solution |\n|-------|-------|----------|\n| Stack traces show minified code | Source maps missing or `--url-prefix` wrong | Re-upload with correct prefix; run `sentry-cli sourcemaps explain` to diagnose |\n| Events not appearing in dashboard | Wrong DSN or network blocked | Verify `SENTRY_DSN` is the production DSN; check firewall allows `*.ingest.sentry.io` on HTTPS |\n| `release` mismatch warning | SDK release differs from CLI release | Ensure `Sentry.init({ release })` matches `sentry-cli releases new $VERSION` exactly |\n| Events from wrong environment | `environment` not set in SDK init | Explicitly set `environment: 'production'` — do not rely on defaults |\n| Excessive event volume \u002F quota exhausted | `sampleRate: 1.0` on high-traffic service | Lower to 0.1-0.25; add `beforeSend` filters; enable server-side inbound filters |\n| Alerts not firing | Alert rules scoped to wrong environment | Edit alert: filter to `environment:production`; test with `Sentry.captureMessage()` |\n| Events lost in serverless \u002F CLI | Process exits before flush | Call `await Sentry.flush(2000)` before `process.exit()` or use `Sentry.wrapHandler()` |\n| `beforeSend` dropping real errors | Overly broad noise filter | Audit filter patterns; log dropped events to a secondary sink during rollout |\n\n## Examples\n\n**Example 1: Full production init (Node.js \u002F Express)**\n\n```typescript\nimport * as Sentry from '@sentry\u002Fnode';\n\nSentry.init({\n  dsn: process.env.SENTRY_DSN,\n  environment: 'production',\n  release: process.env.SENTRY_RELEASE,\n  debug: false,\n  sendDefaultPii: false,\n  sampleRate: 0.25,\n  tracesSampleRate: 0.1,\n  maxBreadcrumbs: 50,\n  attachStacktrace: true,\n\n  ignoreErrors: [\n    'ResizeObserver loop',\n    'Non-Error promise rejection captured',\n    \u002FLoading chunk \\d+ failed\u002F,\n  ],\n\n  beforeSend(event, hint) {\n    if (event.request?.headers) {\n      delete event.request.headers['Authorization'];\n      delete event.request.headers['Cookie'];\n    }\n    return event;\n  },\n\n  tracesSampler: (ctx) => {\n    const name = ctx.transactionContext?.name || '';\n    if (name.includes('\u002Fhealth')) return 0;\n    if (name.includes('\u002Fpayment')) return 1.0;\n    return 0.1;\n  },\n});\n```\n\n**Example 2: CI source map upload (GitHub Actions)**\n\n```yaml\n# .github\u002Fworkflows\u002Fdeploy.yml\n- name: Upload source maps to Sentry\n  env:\n    SENTRY_AUTH_TOKEN: ${{ secrets.SENTRY_AUTH_TOKEN }}\n    SENTRY_ORG: my-org\n    SENTRY_PROJECT: my-project\n    VERSION: ${{ github.sha }}\n  run: |\n    npx sentry-cli releases new \"$VERSION\"\n    npx sentry-cli releases set-commits \"$VERSION\" --auto\n    npx sentry-cli releases files \"$VERSION\" upload-sourcemaps .\u002Fdist \\\n      --url-prefix '~\u002Fstatic\u002Fjs' --validate\n    npx sentry-cli releases finalize \"$VERSION\"\n    npx sentry-cli releases deploys \"$VERSION\" new -e production\n```\n\n**Example 3: Serverless flush pattern (AWS Lambda)**\n\n```typescript\nimport * as Sentry from '@sentry\u002Fnode';\n\nSentry.init({\n  dsn: process.env.SENTRY_DSN,\n  environment: 'production',\n  release: process.env.SENTRY_RELEASE,\n  tracesSampleRate: 0.2,\n});\n\nexport const handler = Sentry.wrapHandler(async (event, context) => {\n  \u002F\u002F wrapHandler automatically calls flush() on completion\n  const result = await processEvent(event);\n  return { statusCode: 200, body: JSON.stringify(result) };\n});\n```\n\n## Resources\n\n- [Sentry Configuration Options](https:\u002F\u002Fdocs.sentry.io\u002Fplatforms\u002Fjavascript\u002Fconfiguration\u002Foptions\u002F) — full SDK init reference\n- [Source Maps Upload](https:\u002F\u002Fdocs.sentry.io\u002Fplatforms\u002Fjavascript\u002Fsourcemaps\u002F) — bundler plugins and CLI upload\n- [sentry-cli releases](https:\u002F\u002Fdocs.sentry.io\u002Fcli\u002Freleases\u002F) — `new`, `set-commits`, `finalize`, `deploys`\n- [Alert Rules](https:\u002F\u002Fdocs.sentry.io\u002Fproduct\u002Falerts\u002F) — issue alerts, metric alerts, uptime monitors\n- [Release Health](https:\u002F\u002Fdocs.sentry.io\u002Fproduct\u002Freleases\u002Fhealth\u002F) — crash-free rates and session tracking\n- [Data Scrubbing](https:\u002F\u002Fdocs.sentry.io\u002Fsecurity-legal-pii\u002Fscrubbing\u002F) — server-side PII removal\n- [Inbound Filters](https:\u002F\u002Fdocs.sentry.io\u002Fproduct\u002Fdata-management-settings\u002Ffiltering\u002F) — server-side event filtering\n\n## Next Steps\n\nAfter completing this production checklist:\n1. **Set up release health monitoring** — track crash-free session rates across releases\n2. **Configure ownership rules** — route issues to the right team based on file paths or error tags\n3. **Add custom dashboards** — build a deployment dashboard showing error rates, P95 latency, and throughput per release\n4. **Schedule quarterly audits** — re-run this checklist after major dependency upgrades or architecture changes\n5. **Enable Session Replay** (if using `@sentry\u002Fbrowser`) — capture user sessions for faster debugging\n",{"name":5,"tags":24,"author":31,"license":15,"version":32,"description":33,"allowed-tools":34,"compatible-with":35},[25,26,27,28,29,30],"saas","sentry","deployment","production","checklist","operations","Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Production deployment checklist for Sentry integration.\nUse when preparing a production deployment, auditing an existing\nSentry setup, or running a go-live readiness review.\nTrigger: \"sentry production checklist\", \"deploy sentry\",\n\"sentry go-live\", \"audit sentry config\", \"production readiness sentry\".\n","Read, Grep, Glob, Bash(npm:*), Bash(npx:*), Bash(node:*), Bash(curl:*), Bash(sentry-cli:*)","claude-code, codex, openclaw","main","99825ad3f3bcc6597ddcc7294a14e6e922f2b67b","skills\u002Fsaas-packs--sentry-pack--sentry-prod-checklist",0,"https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills","https:\u002F\u002Fgithub.com\u002Fjukeyman","https:\u002F\u002FRJBUSINESSSOLUTIONS.ORG","Credit and Finance Expert | Developer\r\n\r\nI'm Rick Jefferson, a seasoned credit and finance expert with over a decade of experience in financial literacy,","2026-07-13 07:03:29",{"source":8,"skillName":5,"commands":46,"prompt":56,"zipAvailable":57},[47,50,53],{"tool":48,"command":49},"npx","npx skills add jukeyman\u002Fjukeyman-skills --skill sentry-prod-checklist",{"tool":51,"command":52},"bunx","bunx skills add jukeyman\u002Fjukeyman-skills --skill sentry-prod-checklist",{"tool":54,"command":55},"pnpm","pnpm dlx skills add jukeyman\u002Fjukeyman-skills --skill sentry-prod-checklist","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsaas-packs--sentry-pack--sentry-prod-checklist\u002FSKILL.md",true,[],[60,67,74,81,88,96],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M79ANS2SM329NEP5ZCX106RR","zustand-store-creator","Create zustand store creator operations. Auto-activating skill for Frontend Development.\nTriggers on: zustand store creator, zustand store creator\nPart of the Frontend Development skill category. Use when working with zustand store creator functionality. Trigger with phrases like \"zustand store creator\", \"zustand creator\", \"zustand\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzustand-store-creator\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M79AMZKP4YDEZ7EHG1Y7PP74","zero-trust-config-helper","Configure with zero trust config helper operations. Auto-activating skill for Security Advanced.\nTriggers on: zero trust config helper, zero trust config helper\nPart of the Security Advanced skill category. Use when configuring systems or services. Trigger with phrases like \"zero trust config helper\", \"zero helper\", \"zero\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzero-trust-config-helper\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M79AMJSBCEJQNBTYNAHYN5HM","zapier-integration-helper","Assist with zapier integration helper operations. Auto-activating skill for Business Automation.\nTriggers on: zapier integration helper, zapier integration helper\nPart of the Business Automation skill category. Use when working with APIs or building integrations. Trigger with phrases like \"zapier integration helper\", \"zapier helper\", \"zapier\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzapier-integration-helper\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M79AHJZGVMARS13VFQYRR1MP","yaml-config-validator","Validate yaml config validator operations. Auto-activating skill for DevOps Basics.\nTriggers on: yaml config validator, yaml config validator\nPart of the DevOps Basics skill category. Use when configuring systems or services. Trigger with phrases like \"yaml config validator\", \"yaml validator\", \"yaml\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fyaml-config-validator\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":92,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M79AHGDZRN0020RDQSQDPAM8","xvary-stock-research","Thesis-driven equity analysis from public SEC EDGAR and market data; \u002Fanalyze, \u002Fscore, \u002Fcompare workflows with bundled Python tools (Claude Code, Cursor, Codex).","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxvary-stock-research\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxvary-stock-research\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":19},"01M79AHCYJ9FV9RMHQ24HDRN33","xss-vulnerability-scanner","Scan xss vulnerability scanner operations. Auto-activating skill for Security Fundamentals.\nTriggers on: xss vulnerability scanner, xss vulnerability scanner\nPart of the Security Fundamentals skill category. Use when working with xss vulnerability scanner functionality. Trigger with phrases like \"xss vulnerability scanner\", \"xss scanner\", \"xss\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxss-vulnerability-scanner\u002FSKILL.md",[],[]]