recipe-persistent-monitor

A long-running monitoring agent automates periodic health checks, cron-based reporting, and webhook triggers while enforcing daily token and cost budgets. You configure adaptive heartbeats, timezone-aware schedules, and rate limiting to maintain production operations safely.

To enforce daily token and cost budgets, the monitoring agent applies rate and token policy enforcement alongside cost tracking. It automatically stops operations when daily budgets are exceeded, preventing runaway usage and unexpected charges.

Yes, you can schedule cron-based daily reports with timezone-aware schedules for weekday operational summaries. This allows the monitoring agent to generate reports at specified times, such as a 9am weekday report, aligned with your operational timezone.

Webhook adapters with secret verification secure external event triggers by validating incoming payloads against a configured secret. This ensures only authenticated events, such as GitHub webhook triggers, are processed by the monitoring agent.

Graceful SIGINT and SIGTERM shutdown handling ensures the persistent monitoring agent stops safely without losing data or leaving operations hanging. It intercepts termination signals to cleanly exit heartbeat loops and cron schedules.

Adaptive heartbeat scheduling skips unnecessary periodic health checks while guaranteeing wake-ups after configurable skip limits. You need it for production monitoring to reduce redundant operations and conserve token budgets without missing critical status checks.