Legal Centre
Monitoring and Alerting Setup
Effective date: 2 March 2026
Paid launch requires live monitoring with named accountability. Monitoring is not considered complete until error ingestion, alert routing, and incident ownership are active.
1. Required Configuration
- Browser, server, and edge Sentry ingestion should be configured with the production DSN and source-map upload enabled.
- A shared alert inbox and a named security incident owner must be configured in production.
- The application surfaces warnings when the DSN, alert inbox, or incident owner email is missing.
2. Minimum Alerts
- Any new unhandled production exception.
- Error volume spikes above the normal baseline.
- Authentication failure spikes.
- Repeated HTTP 429 responses on login or admin endpoints.
3. Launch Verification
- Trigger a test exception in a non-production environment.
- Confirm the event reaches Sentry with release information.
- Confirm the shared alert inbox receives the alert and the incident owner can access the runbook.
4. Ongoing Operations
- Review unresolved production issues at least weekly.
- Revisit alert thresholds after major launches.
- Keep the incident runbook aligned with the live alert flow.