error-tracking

Error tracking with Sentry starts with initializing the SDK in an `instrument.ts` file before your application boots, then importing that file at your app's entry point. This ensures all unhandled exceptions and manual captures are automatically reported to Sentry with full context and performance traces.

Capture exceptions manually using Sentry's SDK methods, attaching custom tags and extra data to provide actionable debugging context. This enriches error reports with user information, request details, and application state, enabling faster diagnosis without manual investigation.

Yes. Sentry's performance monitoring creates spans across controllers, routes, cron jobs, and database queries to track operation timing and identify bottlenecks. This provides visibility into where your application spends time and where optimization efforts should focus.

Sentry supports comprehensive monitoring across frontend and backend. The same initialization patterns and error capture principles apply to both layers, ensuring all errors—regardless of origin—flow into a unified observability platform for centralized debugging.

This Skill enforces mandatory error capture: all errors must be reported to Sentry with no exceptions. Untracked errors remain invisible, preventing you from detecting issues in production and missing opportunities to resolve them before users are impacted.

Integrate Sentry into cron job initialization and workflow handlers using the same instrumentation patterns as controllers and routes. This captures errors and performance data from scheduled tasks and async operations, providing end-to-end observability across your entire service architecture.