Monitoring
Production Monitoring Readiness
WarpIntel keeps production monitoring visible through public-safe counts, deploy signals, health checks, and provider gate states while protected ops details and private EVE data stay out of public pages.
Health, smoke, protected ops, release, telemetry, error, and deploy-link lanes.
Monitoring lanes that are safe to rely on in the current public MVP.
Public routes, public feeds, account boundaries, and protected checks tracked by smoke coverage.
No-secret public JSON and discovery feeds monitored by production smoke.
Public Health Snapshot
- Current Signal
- 165 route-smoke targets tracked through health.
- Public Detail
- Public health exposes aggregate production readiness and release metadata.
- Next Step
- Keep public health green after every deploy.
Route Smoke Coverage
- Current Signal
- 165 total targets and 51 public feeds.
- Public Detail
- Public pages, public feeds, account boundaries, and protected checks are counted.
- Next Step
- Run production live smoke after each release.
Protected Ops Exports
- Current Signal
- 44/44 protected exports covered.
- Public Detail
- Admin-only ops exports stay private while public health reports aggregate coverage.
- Next Step
- Keep protected export routes unauthorized to public visitors.
Status Readiness
- Current Signal
- 173 public-safe status cards represented.
- Public Detail
- The public status surface summarizes app, provider, queue, policy, and consent readiness.
- Next Step
- Keep status links, queue counts, and safety boundaries synchronized with health.
Release Readiness
- Current Signal
- 236 verified release entries.
- Public Detail
- Release history records commit, deployment, verification, links, and safety notes.
- Next Step
- Add a release-ledger entry after each completed production slice.
Vercel/GitHub Deploy Link
- Current Signal
- Production project link is confirmed.
- Public Detail
- Production deploy and repository-link readiness are tracked without provider tokens.
- Next Step
- Confirm provider metadata in the WarpIntel project account before enabling link-dependent automation.
Growth Telemetry
- Current Signal
- 4 growth gates and 4 boundaries tracked.
- Public Detail
- Analytics, speed insights, and search verification stay behind explicit production gates.
- Next Step
- Enable telemetry only after owner approval and provider verification.
Sentry Monitoring
- Current Signal
- Error capture is not active; first-party ops monitoring remains the production source.
- Public Detail
- Provider error capture remains off until DSN, org, project, and sample-capture gates are reviewed.
- Next Step
- Use protected setup and dry-run routes before enabling provider capture.
No-Secret Monitoring Rule
Public monitoring readiness exposes aggregate route-smoke counts, protected-check counts, release counts, readiness booleans, provider gate states, and public links only; it does not expose provider tokens, provider account names, provider cookies, private repository data, raw logs, raw visitor identifiers, EVE tokens, private EVE data, private account data, protected export bodies, protected setup details, or raw pasted analyzer inputs.