vincentbean

<p>Vigilant Healthchecks provides a REST healthcheck endpoint at <code>/wp-json/vigilant/v1/health</code> with an admin interface to conrol which checks are executed.<br />
This plugin is designed to integrate with <a href="https://govigilant.io" rel="nofollow ugc">Vigilant</a>, an all-in-one web monitoring tool which can be self-hosted.</p>
<h4>Key Features</h4>
<ul>
<li>Protected REST endpoint with configurable token.</li>
<li>Built-in checks for database connectivity, core versions, plugin updates, cron freshness, Redis, and WordPress Site Health issues.</li>
<li>Metrics catalogue for memory, disk, CPU load, and database size with sensible caching defaults.</li>
<li>Extensible registry and hooks (<code>vigilant_healthchecks_prepare</code>, <code>vigilant_healthchecks_cron_threshold</code>, <code>vigilant_healthchecks_database_size_cache_ttl</code>) so you can add custom checks and metrics.</li>
<li>Scheduler heartbeat (<code>vigilant_healthchecks_cron_monitor</code>) that validates WP-Cron is actually running and reports stale schedules.</li>
</ul>
<h4>How It Works</h4>
<ol>
<li>Configure the bearer token under <strong>Settings <span aria-hidden="true" class="wp-exclude-emoji">→</span> Vigilant Healthchecks</strong>; every REST request must include <code>Authorization: Bearer <token></code>.</li>
<li>Toggle the checks and metrics you want to expose; disabled items are never instantiated so they have zero runtime impact.</li>
<li>Call the endpoint yourself or configure your website in Vigilant.</li>
</ol>


Vigilant Healthchecks

A WordPress plugin that provides healthchecks to your WordPress site that integrate seamlessly with Vigilant (https://govigilant.io).

cronheart

<p><strong>WP-Cron is request-driven.</strong> On a low-traffic site no requests arrive, no events fire, and a scheduled backup can be stalled for weeks before anyone notices. Uptime monitors do not catch this — the site responds to HTTPS just fine, it just is not running its jobs.</p>
<p>Cronheart turns WP-Cron into a <strong>dead-man switch</strong>: the plugin pings <a href="https://cronheart.com" rel="nofollow ugc">cronheart.com</a> every five minutes and on every individual event you register. If the pings stop, cronheart alerts you via email, Telegram, Slack, Discord, or a custom webhook.</p>
<h4>What it does</h4>
<ul>
<li><strong>Site heartbeat.</strong> A 5-minute custom WP-Cron event whose only job is to ping cronheart. Proves WP-Cron itself is alive on this site.</li>
<li><strong>Per-event monitoring.</strong> Register any scheduled hook for start / success / fail pings with one PHP one-liner: <code>cronheart_monitor( 'my_nightly_report', 'xxxxxxxx-…' );</code></li>
<li><strong>PHP fatal-error capture.</strong> When a scheduled callback fatals or throws, the fail-ping body includes the <code>error_get_last()</code> summary — the cronheart dashboard shows the cause without you tailing <code>debug.log</code>.</li>
<li><strong>Settings page.</strong> A read-only “Monitored events” table at Settings <span aria-hidden="true" class="wp-exclude-emoji">→</span> Cronheart shows every hook the plugin is watching and where its UUID came from (constant, option, filter).</li>
<li><strong>Monitor picker.</strong> Save a cronheart.com API token and the site heartbeat field becomes a dropdown of your account’s monitors instead of a hand-typed UUID. Entirely optional — without a token you paste the UUID as before, and any API hiccup falls back to that field. The token is write-only and never leaves wp-admin.</li>
<li><strong>Configuration through <code>wp-config.php</code> constants</strong> for production (<code>CRONHEART_HEARTBEAT_UUID</code>, <code>CRONHEART_EVENT_<HOOK>_UUID</code>), with admin-UI fallback for sites where editing <code>wp-config.php</code> is not practical.</li>
</ul>
<h4>Never breaks WP-Cron</h4>
<p>The plugin’s hard contract: a broken cronheart backend, an unreachable network, a misbehaving PSR-18 HTTP client — none of them may cause WP-Cron to fail. Every network / HTTP error is swallowed into a logged warning. If cronheart goes down for a day, your <code>wp_schedule_event</code> callbacks still run normally; you just stop seeing pings on the dashboard.</p>
<h4>External services</h4>
<p>This plugin sends HTTP requests to <a href="https://cronheart.com" rel="nofollow ugc">cronheart.com</a> in two distinct situations. Both are opt-in: without configuration the plugin loads and does nothing — no telemetry, no usage statistics, no anonymous reports.</p>
<p><strong>1. Monitoring pings (front end / WP-Cron).</strong> Sent on every scheduled WP-Cron run, but <strong>only when you supply a monitor UUID</strong>. The exact data sent per ping:</p>
<ul>
<li>The per-monitor UUID you configured (path segment).</li>
<li>A short body excerpt — capped at 10 KB — containing either an exception summary (for <code>fail</code> pings) or nothing (for <code>start</code> / <code>success</code> / <code>heartbeat</code>).</li>
<li>The plugin / SDK version in a <code>User-Agent</code> header.</li>
</ul>
<p><strong>2. Monitor listing (wp-admin only).</strong> When — and only when — you save a cronheart.com API token, the <strong>Settings <span aria-hidden="true" class="wp-exclude-emoji">→</span> Cronheart</strong> page calls <code>https://cronheart.com/api/v1/monitors</code> to fetch your monitor list for the heartbeat picker. The request carries the token as an <code>Authorization: Bearer</code> header and runs <strong>only while a logged-in administrator is viewing that settings page</strong> — never on the front end, during WP-Cron, or in any other context. No token, no request. The token is optional; without it you simply paste a monitor UUID by hand and this call is never made.</p>
<p><a href="https://cronheart.com/terms" rel="nofollow ugc">Cronheart.com Terms of Service</a> · <a href="https://cronheart.com/privacy" rel="nofollow ugc">Privacy policy</a></p>
<h4>Open source</h4>
<p>Source code and issue tracker: <a href="https://github.com/alexander-po/cronheart-wp" rel="nofollow ugc">github.com/alexander-po/cronheart-wp</a>.</p>
<p>The plugin wraps the <a href="https://github.com/alexander-po/cron-monitor-php" rel="nofollow ugc"><code>cron-monitor/php-sdk</code></a> PHP package (also open source, MIT-licensed). Both projects are maintained independently.</p>


Cronheart

Dead-man-switch monitoring for WP-Cron. Get alerted when scheduled events stop firing — uptime monitors do not catch this.

Vigilant Healthchecks vs Cronheart