Purpose
This timer collects operational metrics — including deal counts, agent activity, and queue depths — and writes them to Supabase. It ensures real-time dashboard views remain current for monitoring system health and performance.
Schedule
OnUnitActiveSec=60s
Runs every 60 seconds after the last activation (AccuracySec=5s for tight timing), with a 30s boot delay (OnBootSec=30s) and a 10s randomized jitter to prevent resource stampedes.
Service
Runs dashboard-metrics.service, which executes the Node.js script located at:
/home/opsadmin/.openclaw/workspace/scripts/dashboard-metrics-cron.js
Failure behavior
The service is configured as a oneshot type. Failures are captured in the systemd journal. No automatic retry is specified in the unit file; failures result in a gap in the metrics timeline until the next 60s tick.
Health signal
Verification can be performed via:
- Systemd Status:
systemctl --user status dashboard-metrics.timer - Logs:
journalctl --user -u dashboard-metrics.service - Data Sink: Verify new timestamped entries in the Supabase metrics tables (CCP project
svueekfvfrvhylxygktb).
Related
- cron-timer-registry — Central registry of all system timers.
- supabase — Destination for collected metrics data.