Server Status

18.1. Server Status — Watching Over the Server

The most basic monitoring job

/cron add "every 2h" "Check server status and alert if down"

This is the classic opening example in every cron guide — a simple job, no special skill needed, just the agent checking and speaking up only when there is a problem.

A sample more comprehensive health-check job

hermes cron create "hourly" \
  "Check: API connectivity, memory usage, model availability. Report any issues" \
  --deliver telegram

Notes

• For simple periodic checks (ping, HTTP status code, disk usage), prefer --no-agent --script — there is no reason to spend an LLM call just to check whether the server responds with 200.
• Pair this job with backups (1.6) — watching server status frequently is an early way to detect signs of VPS trouble before it affects other important cron jobs.
• Set a frequency appropriate to the importance level — a production system should be checked more often (every 15-30 minutes) than a personal project (every few hours is enough).