Error Monitoring
Sentry Readiness
WarpIntel can prepare provider error monitoring while keeping DSN values, provider identifiers, event URLs, stack traces, cookies, authorization headers, private EVE data, and protected setup details out of public pages, health snapshots, smoke logs, screenshots, and readiness feeds.
Public Sentry readiness is aggregate only; provider setup evidence remains protected.
Error capture stays off until the provider lane is configured, reviewed, and verified.
Setup packet, dry-run, and activation rehearsal checks stay behind admin-only routes.
Dry runs do not capture events, contact provider APIs, or expose DSN state.
A future sample capture must pass no-secret owner review before provider capture is enabled.
Operator handoff steps define the protected sample-capture review sequence.
Capture setup has public-safe rollback decisions before any provider event is accepted.
Capture stays gated until all public-safe activation criteria are ready.
Protected rehearsal evidence stays no-capture, no-provider-mutation, and count-only publicly.
Provider Mutation
Activation rehearsals do not call Sentry, mutate provider settings, upload sourcemaps, or change flags.
Event Capture
The protected rehearsal packages evidence only and does not capture a Sentry event.
Provider Identifiers
DSNs, org/project values, auth tokens, event URLs, and stack traces remain excluded from public output.
WarpIntel-only provider boundary
Protected setup guidance requires a WarpIntel-only Sentry project and excludes separate-project provider crossover.
Feature flag and DSN gate
Provider capture remains inactive unless the explicit public Sentry feature gate and a WarpIntel DSN presence check are both ready.
Provider project review gate
Provider organization and project routing must be staged in protected configuration before sample capture review.
Installed instrumentation gate
Browser, server, and edge instrumentation are installed behind an explicit capture gate.
Private data scrub gate
Seven scrub-rule families redact authorization headers, cookies, tokens, DSNs, private user fields, nested context, and sensitive breadcrumbs.
Protected dry run without provider call
Protected dry runs validate readiness without calling Sentry, capturing events, returning DSNs, or reading private app/account data.
Sample capture criteria ready
The future sample event must pass all protected no-secret sample-capture criteria before provider capture is enabled.
Owner-reviewed sample capture gate
A non-sensitive protected sample capture must be owner-reviewed and recorded before Sentry capture can initialize.
Provider Boundary Confirmed
Confirm the future capture uses only WarpIntel provider configuration and no separate-project assets.
Safe Trigger Route Prepared
Prepare a protected admin-only trigger that returns no event payload, provider URL, or private request data.
Scrub Preview Reviewed
Review the locally scrubbed preview before any provider capture can be enabled.
Provider Event Reviewed
Review one non-sensitive provider event for no secrets, cookies, tokens, or private EVE data.
Trigger Disabled
Remove or disable the temporary trigger immediately after the sample event is reviewed.
Release Tracker Recorded
Record only secret-free commit, deployment, route, and review outcomes in the tracker.
Provider Boundary Mismatch
Boundary mismatch stops activation before any provider event is accepted.
Scrub Preview Failure
Scrub failure keeps provider capture off until the local no-secret proof passes.
Unexpected Capture Activity
Unexpected capture activity rolls the lane back to public health and protected dry-run monitoring.
server errors
Represented in public readiness as aggregate status only; provider-side event details stay protected.
browser errors
Represented in public readiness as aggregate status only; provider-side event details stay protected.
performance traces
Represented in public readiness as aggregate status only; provider-side event details stay protected.
Dsn Values
Excluded from public pages, health snapshots, smoke logs, screenshots, and readiness feeds.
Provider Org Identifiers
Excluded from public pages, health snapshots, smoke logs, screenshots, and readiness feeds.
Provider Project Identifiers
Excluded from public pages, health snapshots, smoke logs, screenshots, and readiness feeds.
Event Urls
Excluded from public pages, health snapshots, smoke logs, screenshots, and readiness feeds.
Stack Traces
Excluded from public pages, health snapshots, smoke logs, screenshots, and readiness feeds.
Cookies
Excluded from public pages, health snapshots, smoke logs, screenshots, and readiness feeds.
Authorization Headers
Excluded from public pages, health snapshots, smoke logs, screenshots, and readiness feeds.
Eve Tokens
Excluded from public pages, health snapshots, smoke logs, screenshots, and readiness feeds.
Private Account Data
Excluded from public pages, health snapshots, smoke logs, screenshots, and readiness feeds.
Raw Pasted Inputs
Excluded from public pages, health snapshots, smoke logs, screenshots, and readiness feeds.
Protected Setup Details
Excluded from public pages, health snapshots, smoke logs, screenshots, and readiness feeds.
No-Secret Sentry Rule
Public Sentry readiness exposes aggregate gate counts, activation criteria, protected-check booleans, activation-rehearsal counts, scrub-rule counts, sample-capture criteria counts, owner-handoff counts, rollback decision counts, capture-off status, instrumentation status, sample-capture status, no-provider-mutation rehearsal status, and no-provider-call dry-run status only; it does not expose DSN values, provider org or project identifiers, event URLs, stack traces, cookies, authorization headers, EVE tokens, private account data, or raw pasted analyzer inputs.