error-tracking

To capture runtime errors and prevent silent failures, enforce Sentry.captureException in every catch block across controllers, services, and cron jobs. Attach contextual metadata like service and operation tags to ensure all exceptions are visible and actionable for debugging.

Contextual metadata for exception capture in asynchronous flows is added by tagging Sentry reports with service, operation, and extra context. This consistent tagging ensures failure visibility and prioritizes actionable diagnostics across all asynchronous code paths.

Consistent error handling patterns are enforced by applying mandatory Sentry.captureException usage with tagged context to all controllers, services, and cron jobs. This ensures uniform failure visibility and proper rethrow or handling behavior across the codebase.

Silent catch blocks hamper reliability by hiding runtime errors and poorly contextualized exceptions. Implementing mandatory Sentry.captureException usage with extra context fixes this by making all error paths report failures with actionable diagnostics.

Yes, this error tracking approach explicitly covers cron jobs and asynchronous flows. It ensures that every catch path in these asynchronous contexts reports to Sentry with contextual metadata, enforcing consistent tagging and proper rethrow behavior.

Basic Sentry captureException without contextual logging limits actionable diagnostics and results in poorly contextualized exceptions. Enriching telemetry with service, operation, and extra context is mandatory to ensure issues are visible and actionable for debugging.