OpenBench monitoring
-
- Bench state on main (prod = openchainbench.com)
- and dev (staging-openchainbench.vercel.app).
- Refreshed every 30s.
-
- How does it work? -
-
- One row per bench. Left side shows its state on main (prod = openchainbench.com),
- right side on dev (staging). Click the green SHA to open
- the bench page in the matching environment.
-
- DRIFT: both branches have the YAML but contents differ. - Usually staging holds updates that haven't been promoted to prod yet. -
-- STAGING ONLY: bench exists on staging only. - Invisible on openchainbench.com until you click → prod. -
-
- → prod: copy the YAML from dev to main, open
- an auto-merged PR, and trigger a Vercel prod deploy. Confirmation modal where you must type
- PROD before execution.
-
- ← remove: delete the YAML on main (kept on dev). - Bench disappears from openchainbench.com after deploy but stays accessible on staging. - Same confirmation modal. -
-
- Prod ETA ≈ 3-5 min after the click. The merged PR
- triggers the prod-deploy.yml GitHub Actions workflow that builds and deploys via
- the Vercel CLI. The result panel exposes a follow CI deploy link to watch the run live.
-
- source link: opens the harness or YAML source on GitHub.
- logs button: hits the harness /logs{" "}
- endpoint (X-Logs-Token auth) on the matching Railway / OVH service. Multi-region benches
- (aggregator-head-lag, rpc-capabilities, solana-dex-quote-latency) expose one button per region.
-
| Bench | -Prod (main) | -Staging (dev) | -Status | -Harness | -Source | -Logs | -Actions | -
|---|---|---|---|---|---|---|---|
|
- {row.entry.slug}
-
- {row.entry.name}
-
- {row.status === "drift" && (
-
- view diff ↗
-
- )}
- |
-
- |
-
- |
-
- |
-
- |
-
- |
-
- |
-
- |
-