Skip to content

M9-14 Production Monitoring & Alerting

Milestone: M9 — Hardening and Compliance SOW Reference: Appendix 6 Operational Requirements; OR3 Requirement Clarity: ✅ Clear Dev Status: ❌ Not started — no monitoring/alerting or integration-health-check infrastructure exists in the codebase

Overview

Appendix 6 explicitly requires the solution to "include monitoring and alerting" and "include health monitoring of integrations," and OR3 requires "the ability to generate key system analytics to track performance metrics such as load, response times, etc." This is a production operational capability distinct from the one-off performance test in M9-08.

Tasks

  • Stand up monitoring/alerting (e.g. AWS CloudWatch, or equivalent depending on the hosting decision at M4-01)
  • Monitor integration health (Velocity Credential Agent, Registrar, Verification Platform, email service) — note the platform's own admin dashboard (M3-10) already surfaces some integration-health data; confirm whether that satisfies this requirement or whether separate ops-facing monitoring/alerting is also expected
  • Set up alerting thresholds for load/response-time degradation

Dependencies

Acceptance Criteria

Not explicitly listed in Appendix 3 — worth adding an explicit criterion once scope (ops-facing vs. admin-dashboard) is confirmed.

Existing Reference Material

  • SOW Appendix 6, "Operational Requirements"; OR3

Blockers & Risks

  • Needs decision: whether this is meant to be a separate ops tool or is already satisfied by the existing admin dashboard's integration-health section.