Sandbox & Backfill
Rule Sandbox
Sandbox runs evaluate a single rule without writing production compliance artifacts.
You can run sandbox with:
ruleId(existing rule), or- A draft rule payload
And target traces by:
- Explicit
traceIds(up to 100), or recentCount(up to 100 latest traces)
Results include per-trace output (PASS, FAIL, WARN, SKIP) and details. No evaluation records, alerts, reviewer-queue items, or audit-log rows are persisted.
Historical Backfill
Backfill re-enqueues compliance evaluation for historical traces after rule-policy changes.
Supported strategies:
| Strategy | Behavior |
|---|---|
NEW_ONLY | Evaluate only newly ingested traces (no historical enqueue) |
LAST_7_DAYS | Re-evaluate traces from the last 7 days |
LAST_30_DAYS | Re-evaluate traces from the last 30 days |
LAST_90_DAYS | Re-evaluate traces from the last 90 days |
FULL | Re-evaluate all traces in the project |
Backfill Controls
- Preview includes estimated trace count and ETA
- Historical backfill is capped at
100,000traces per run - Backfill status reports processed and failed counts via batch-action tracking
Operational Notes
- Backfill evaluations update compliance records, alerts, and reviewer queue as needed
- Daily compliance aggregate counters are ingestion-first-evaluation metrics, not manually rerun/backfill counters