error-tracking

To set up Sentry v8 error tracking, initialize Sentry instrumentation at startup in each backend service. This captures errors and performance data across controllers, routes, and database operations using structured patterns.

Monitor database performance and cron job errors by applying Sentry v8 instrumentation helpers like DatabasePerformanceMonitor. This ensures structured error capture and context-rich reporting for scheduled tasks and database operations.

Add structured error handling to API routes by implementing Sentry initialization and using context-rich reporting helpers like WorkflowSentryHelper. This enforces consistent error capture across all backend routes.

Yes, Sentry initialization supports configurable per-environment settings for each backend service. This allows distinct error tracking and performance monitoring configurations across development, staging, and production environments.

Backend errors are missed when Sentry v8 initialization is not applied at service startup or structured error handling patterns are bypassed. Enforcing consistent instrumentation across controllers and cron jobs ensures every error is captured.