Skip to content

[ENHANCEMENT] Add Sentry or equivalent error tracking integration #119

Description

@kilodesodiq-arch

Engineering Gap

No centralized error tracking or alerting. Production errors discovered only through user reports. Error handling exists (exception filter, error boundaries) but no aggregation or alerting.

Codebase Evidence

  • app/backend/src/common/filters/http-exception.filter.ts: Catches all exceptions but only logs locally
  • app/frontend/src/components/ErrorBoundary.tsx: Catches React errors but only console.error
  • No Sentry, DataDog, or similar SDK in any package.json

Risk Profile

Production errors invisible. User-reported bugs only. No error trend analysis.

Remediation Strategy

Add Sentry SDK to backend, frontend, and mobile. Configure error sampling, PII scrubbing, and environment separation. Add alerting for error rate spikes.

Success Conditions

  • Sentry SDK added to backend
  • Sentry SDK added to frontend
  • Error sampling configured
  • PII scrubbing configured

Change Surface

Files: package.json files, main.ts, ErrorBoundary.tsx, env configuration

Security Review

Error data must be scrubbed of PII before sending to Sentry.

Completion Checklist

  • Implementation completed
  • Peer reviewed
  • Security review completed
  • Ready for merge

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions