p2-implement-sentry

drafttype/backlog

Backlog: Implement Sentry

TL;DR

Add Sentry to LumenDev Invoice for error monitoring, release tracking, and actionable stack traces in preview/production.

Description

  • Problem / user story: Failures in API routes, PDF generation, and Mongo interactions need centralized visibility.
  • Context / constraints: Next.js App Router SDK; separate DSNs per env; avoid logging PII; keep sampling sensible for cost.

Acceptance Criteria

  • [ ] Sentry initialized for server and client surfaces used by the app; source maps/upload story documented or scripted.
  • [ ] Test error verifies events in Sentry in non-prod.
  • [ ] Runbook note or hub pointer for “how to triage” (link from project hub or runbooks when added).

Priority

  • Priority: p2
  • Rationale: Improves MTTR once auth and outbound notifications ship.

Dependencies

  • Blocks:
  • Blocked by:
  • Related ADR:

Links

  • Project context: [[Projects/lumendev-invoice/context/index]]
  • Design / Spec:
  • Ticket / Issue:

Notes

  • Origin: inbox capture Lumen Invoice app todos (processed 2026-05-17).