Error monitoring review
Sentry Reviewer Workflow
This reviewer board ties Sentry activation proof together before provider capture can be enabled. It shows provider-boundary gates, scrub rules, sample-capture owner review, activation rehearsal, rollback paths, and production proof links without exposing DSN values, provider identifiers, event URLs, stack traces, cookies, private EVE data, or protected setup packet bodies.
3 lanes are ready and 4 block capture.
WarpIntel-only provider setup stays protected until final owner review.
Headers, cookies, request data, token fields, identifiers, context, and breadcrumbs are scrubbed.
A future sample event must be non-sensitive, protected, reviewed, and removed after use.
Setup packet, dry run, and activation rehearsal remain admin-only.
Protected rehearsal proves no provider mutation, no Sentry call, and no event capture.
Provider mismatch, scrub failure, and unexpected capture activity have stop paths.
Public text excludes DSNs, provider identifiers, stack traces, tokens, and private data.
WarpIntel Provider Boundary
2/10 Sentry gates are ready without exposing DSNs or provider identifiers.
Use a WarpIntel-only Sentry project and keep all provider values in protected configuration.
Scrub Rules And Event Preview
7 scrub rules cover headers, cookies, request payloads, tokens, user identifiers, nested context, and breadcrumbs.
Keep local scrub preview proof protected before any provider capture is approved.
Sample Capture Owner Handoff
6/6 owner review steps are mapped for a future non-sensitive sample event.
Record only public-safe sample-capture outcomes; keep provider event URLs and stack traces protected.
Protected Activation Rehearsal
8 rehearsal gates and 8 proof targets stay protected and no-capture.
Run protected rehearsal before enabling capture; do not expose rehearsal bodies publicly.
Capture Gate
Capture is off and safe-to-enable is blocked.
Enable capture only after WarpIntel-only DSNs, owner approval, scrub proof, and sample review are complete.
Rollback Paths
3 rollback paths cover provider mismatch, scrub-preview failure, and unexpected capture activity.
Keep rollback decisions visible before any live provider event is accepted.
Production Proof Links
Health, status, monitoring, security, integrations, releases, and smoke targets remain linked for production review.
After any Sentry activation, rerun live smoke and record release/tracker evidence.
Sentry Reviewer page
Public page renders the Sentry review workflow without protected setup bodies.
Sentry Reviewer JSON
Machine-readable reviewer feed exposes aggregate Sentry review counts only.
Sentry Readiness page
Readiness page shows public Sentry gates and no-secret boundaries.
Sentry Readiness JSON
Readiness feed excludes DSNs, provider identifiers, event URLs, and stack traces.
Protected Sentry setup packet
Protected setup route exists but stays admin-only.
Protected Sentry dry run
Protected dry run validates no-provider-call boundaries.
Protected activation rehearsal
Protected rehearsal keeps provider mutation and event capture off.
Health JSON
Public health includes Sentry readiness and smoke counters.
Status
Public status is the production operator surface.
Monitoring
Monitoring readiness links Sentry capture-off proof.
Integrations
Provider setup remains grouped without exposing account details.
Security
Security policy is linked for capture and disclosure review.
Ops Readiness
Ops readiness proves protected export boundaries.
Next Actions
Next actions keeps buildable and blocked Sentry work separated.
Release Readiness
Release readiness tracks deployment proof.
Releases
Release notes record each production change.
Visibility
Kept out of public pages, health snapshots, smoke logs, screenshots, and readiness feeds.
Source Data
Kept out of public pages, health snapshots, smoke logs, screenshots, and readiness feeds.
Dsn Values
Kept out of public pages, health snapshots, smoke logs, screenshots, and readiness feeds.
Provider Org Identifiers
Kept out of public pages, health snapshots, smoke logs, screenshots, and readiness feeds.
Provider Project Identifiers
Kept out of public pages, health snapshots, smoke logs, screenshots, and readiness feeds.
Event Urls
Kept out of public pages, health snapshots, smoke logs, screenshots, and readiness feeds.
Stack Traces
Kept out of public pages, health snapshots, smoke logs, screenshots, and readiness feeds.
Cookies
Kept out of public pages, health snapshots, smoke logs, screenshots, and readiness feeds.
Authorization Headers
Kept out of public pages, health snapshots, smoke logs, screenshots, and readiness feeds.
Eve Tokens
Kept out of public pages, health snapshots, smoke logs, screenshots, and readiness feeds.
Private Account Data
Kept out of public pages, health snapshots, smoke logs, screenshots, and readiness feeds.
Raw Pasted Inputs
Kept out of public pages, health snapshots, smoke logs, screenshots, and readiness feeds.
Protected Setup Bodies
Kept out of public pages, health snapshots, smoke logs, screenshots, and readiness feeds.
Provider Calls
Kept out of public pages, health snapshots, smoke logs, screenshots, and readiness feeds.
Provider Mutations
Kept out of public pages, health snapshots, smoke logs, screenshots, and readiness feeds.
Event Capture
Kept out of public pages, health snapshots, smoke logs, screenshots, and readiness feeds.
Database Writes
Kept out of public pages, health snapshots, smoke logs, screenshots, and readiness feeds.
Separate Project Accounts
Kept out of public pages, health snapshots, smoke logs, screenshots, and readiness feeds.
No-Secret Sentry Reviewer Rule
Public Sentry reviewer exposes aggregate provider-boundary counts, scrub-rule counts, sample-capture criteria counts, owner-handoff counts, activation-rehearsal counts, rollback counts, protected packet labels, production proof links, and no-secret safety booleans only; it does not expose DSN values, provider org identifiers, provider project identifiers, event URLs, stack traces, cookies, authorization headers, EVE tokens, private account data, raw pasted inputs, separate-project account details, or protected setup packet bodies, and it does not call Sentry, capture events, mutate provider state, upload sourcemaps, write database rows, or start EVE OAuth.