error-tracking

Sentry v8 error tracking captures all exceptions across controllers, routes, workflows, and cron jobs. You initialize Sentry at startup and instrument new code paths to guarantee no silent failures or missed errors.

Sentry performance monitoring provides tracing and spans for fast feedback on latency and database interactions. You instrument code paths using patterns like DatabasePerformanceMonitor to track database performance bottlenecks.

Structured context in Sentry error tracking adds user, environment, and operation data to captured exceptions. This enables rapid debugging and incident response by providing full visibility into the exact state when errors occur.

Cron job instrumentation captures errors and monitors performance by applying Sentry v8 during execution. You initialize Sentry and use specific usage patterns to ensure cron workflows have comprehensive error visibility.

Sentry v8 works with controllers and workflows by applying patterns such as BaseController and WorkflowSentryHelper. This enforces unified error capture across all project services to eliminate ad-hoc logging.

Sentry initialization at startup is required for error tracking to establish proper context and usage patterns. Without it, code paths cannot capture errors with the necessary environment and user data for effective debugging.