aiwf:error-tracking

Error capturing with Sentry requires universal v8 integration initialization across all project services. The Skill enforces comprehensive error tracking patterns for controllers, routes, workflows, and cron jobs, ensuring errors surface in Sentry dashboards with contextual metadata, user tagging, and environment data instead of being logged only to console.

Sentry v8 workflow and cron support captures scheduled task errors with performance tracing. The Skill implements standardized error handling patterns that integrate cron jobs and workflows into your error monitoring, guaranteeing visibility into failures that would otherwise go undetected in background processes.

Yes. Sentry v8 performance monitoring tracks database queries through dedicated performance spans. The Skill enforces database performance instrumentation as part of comprehensive monitoring, capturing query execution alongside errors to identify bottlenecks and failures in data layer operations.

Sentry initialization must occur in service instrumentation for each project service. The Skill provides standardized initialization patterns that you apply consistently—such as in blog-api or notifications services—to ensure all services report errors and performance data to the same Sentry project.

Console logs are ephemeral and lack aggregation; Sentry provides persistent, searchable error dashboards with automatic grouping, context, and performance traces. The Skill enforces this distinction by ensuring all errors reach Sentry with standardized metadata, making errors visible, actionable, and traceable across your infrastructure.

Sentry error capture requires contextual metadata including user identification, environment tagging, and request context. The Skill enforces standardized metadata patterns across controllers and routes, ensuring errors include relevant identifiers and environment details so errors are traceable and debuggable in dashboards.