Error tracking service is configured in production

Without an error tracking service, production failures are invisible until users report them — often via churn, refund requests, or social media. NIST SP 800-53 SI-11 requires software fault handling that produces meaningful diagnostic output; console.error into a log file no one monitors does not meet that bar. ISO 25010 reliability.fault-tolerance depends on detection: you cannot respond to a fault you cannot observe. A free-tier Sentry account covers most production workloads and takes under 30 minutes to configure.

Integrate Sentry (free tier covers most projects) or an equivalent service. Configure both frontend and backend capture in the same setup.

// instrumentation.ts (Next.js) or app entry point
import * as Sentry from '@sentry/nextjs'

Sentry.init({
  dsn: process.env.SENTRY_DSN,
  environment: process.env.NODE_ENV,
  tracesSampleRate: 0.1, // 10% performance tracing
})

Verify the integration by deliberately throwing a test error in development and confirming it appears in the Sentry dashboard within 60 seconds. Then configure at least one alert rule (error rate threshold or new-issue notification) before marking this check complete.