Error tracking tool installed and configured

Severity: Critical

Error tracking is essential for production visibility. Without it, you're flying blind when users encounter errors.

Check automatically:

1. Look for Sentry SDK:

# Check for Sentry packages
grep -riE "@sentry|sentry-javascript|@sentry/node|@sentry/browser|@sentry/react|@sentry/nextjs" package.json 2>/dev/null

# Check for Sentry DSN configuration
grep -riE "SENTRY_DSN|sentry\.dsn|dsn.*sentry" .env.example .env* 2>/dev/null

# Check for Sentry initialization
grep -riE "Sentry\.init|sentry\.init" --include="*.ts" --include="*.js" --include="*.tsx" src/ lib/ app/ 2>/dev/null | head -10

2. Check for alternative error tracking tools:

# Bugsnag, Rollbar, Raygun, TrackJS, Airbrake
grep -riE "bugsnag|rollbar|raygun|trackjs|airbrake" package.json .env.example 2>/dev/null

3. Verify initialization runs early:

# Check entry points for early Sentry init
head -50 src/index.ts src/main.ts src/app.ts app/layout.tsx pages/_app.tsx 2>/dev/null | grep -iE "sentry|error.*tracking"

If not found in code, ask user:

• "What error tracking tool do you use?"
• "Is it configured for both frontend and backend?"

Cross-reference with:

• ERR-005 (deployment integration requires error tracking to exist)
• MON-004 (500 alerting may come from error tracker)

Pass criteria:

• Error tracking SDK installed and initialized
• DSN configured (or env var placeholder in .env.example)
• Initialization runs early in app startup (before route handlers)

Fail criteria:

• No error tracking tool found
• SDK installed but never initialized
• DSN missing with no placeholder

Evidence to capture:

• Error tracking tool name and version
• DSN env var configuration
• Initialization location in code

---