heartbeat

Configure automated heartbeat monitoring by editing the HEARTBEAT.md file to define file-watch, shell-command, and url-health checks. The system enforces these TOML-based settings at runtime to validate service health and trigger alerts for your Nextcloud-backed environments.

Yes, heartbeat monitoring supports quiet hours, default cooldowns, and per-check cooldowns to control alert noise. You can also specify per-check intervals to balance timely failure detection with alert suppression during configured quiet periods.

You can automate file-watch, shell-command, and url-health checks for AI agent workflows. These check types validate file availability, service health, and API responses, triggering alerts on failures to ensure system availability.

Yes, the system uses a TOML-based settings schema to specify per-check rules for your service health checks. This schema defines intervals, cooldowns, and quiet hours that the runtime enforces when validating API responses and file availability.

The best way to detect downtime is deploying automated heartbeat monitoring with configurable intervals. By defining url-health and file-watch checks in your config, the system validates availability and triggers immediate alerts upon detecting failures.

Heartbeat checks may not trigger alerts if quiet hours are active or per-check cooldowns have not elapsed. Verify your TOML settings schema to ensure intervals are configured correctly and cooldown periods are not suppressing failure notifications.