Supervising 13 always-on processes without Kubernetes: the log-freshness health check that ended my 3 a.m. babysitting

Из ленты dev.to devops — кратко, чтобы не потерять.

I’m a solo builder. At any given moment I have a handful of always-on processes earning, scraping, or thinking on my behalf: a Polymarket crash-recovery trading bot, a weekly site-scraper that regenerates a ~14k-entry directory, a couple of API servers, a secret-scanner, a DB-retention job, and a few scheduled agents that call an LLM to review strategy or hunt vulnerabilities. Thirteen in total. For months these lived as a mess of launchd plists, loose crontab lines, and nohup … & processes I’d forget about until one silently died — and I’d notice days later, usually because a number on a dashboard stopped moving. That’s the classic agent-ops failure mode: lots of independent autonomous processes, no unified supervisor. Each one is individually simple. Collectively they’re un-auditable. I

Полный текст и контекст у первоисточника: https://dev.to/manja316/supervising-13-always-on-processes-without-kubernetes-the-log-freshness-health-check-that-ended-my-4g4l