Monitors
Schedule a collection or folder to run automatically on an interval and track pass/fail history — no external cron needed.
A monitor is a saved "run this collection/folder on a schedule" definition, executed by the running server.js process itself — no external cron, and no browser tab needs to stay open. It reuses the exact same headless run logic as the CLI Runner (lib/headless-runner.js), invoked in-process against the server's own port on an interval.
Click Monitors in the topbar to open the modal:
- Click + New Monitor, give it a name, and pick a Collection (and optionally a Folder to run instead of the whole collection).
- Optionally pick an Environment — leave it on "Active environment" to always use whatever's currently selected in the topbar.
- Set the Interval (minutes) and make sure Enabled is checked, then click Create.
- Click Run Now at any time for an immediate run without waiting for the schedule.
Each monitor keeps its most recent runs (status, elapsed time, requests/tests passed) under Recent runs in its detail panel, and a colored dot next to its name in the list shows the outcome of its last run at a glance (green = passed, red = failed, grey = never run). A dot also lights up on the topbar Monitors button whenever any enabled monitor's last run failed.
Monitor definitions live in data/_volley/monitors.json and sync via Git Sync like any other collection config; run history lives in data/_volley/monitor-runs.json and is excluded from sync, same as request history — see Data Storage.