[WordPress] 外掛分享: CronVitals – WP-Cron Monitoring & Failure Alerts

首頁外掛目錄 › CronVitals – WP-Cron Monitoring & Failure Alerts
WordPress 外掛 CronVitals – WP-Cron Monitoring & Failure Alerts 的封面圖片
全新外掛
安裝啟用
尚無評分
14 天前
最後更新
問題解決
WordPress 5.8+ PHP 7.4+ v1.0.0 上架:2026-08-31

內容簡介

CronVitals 是一款專為監控 WP-Cron 設計的外掛,能夠追蹤網站上所有排程任務的執行狀態,並在任務失敗時發送警報,確保網站運行的可靠性與穩定性。

【主要功能】
• 監控所有 WP-Cron 任務的執行狀態
• 記錄每次任務的執行時間與結果
• 提供失敗任務的詳細錯誤訊息
• 設定未執行任務的警報閾值
• 自動收集並保存 30 天的歷史記錄

外掛標籤

開發者團隊

⬇ 下載最新版 (v1.0.0) 或搜尋安裝

① 下載 ZIP → 後台「外掛 › 安裝外掛 › 上傳外掛」
② 後台搜尋「CronVitals – WP-Cron Monitoring & Failure Alerts」→ 直接安裝(推薦)
📦 歷史版本下載

原文外掛簡介

A scheduled post didn’t publish. A subscription didn’t renew. Stock didn’t sync. WordPress never told you — WP-Cron fails silently, and by the time someone notices, it’s a client email.
CronVitals is a monitor for WP-Cron. It watches every scheduled job on your site, records every run, and tells you when one breaks.

See the actual error, not just “something failed.” When a cron job dies on a PHP fatal, CronVitals catches it during shutdown and logs the message, file, and line — the thing that’s normally lost because nobody was watching the request.
Catch jobs that never ran at all. A configurable threshold (default 15 minutes past schedule) marks a job as missed, so a job that quietly stopped rescheduling shows up as a problem instead of just disappearing.
Answer “how long has this been broken?” Every run is logged — job, scheduled time, actual run time, duration, pass/fail — with 30 days of history, a reliability score, and a per-job failure breakdown.

How it works

Activate. Every registered WP-Cron event is picked up automatically — no list to build, no jobs to register.
Set the alert email and the missed-run threshold under Tools → CronVitals. That’s the whole setup.
You get an email (rate-limited, never a flood) and a dashboard notice when a job fails or runs late.

What it actually does under the hood
CronVitals attaches to each monitored hook at the outermost priorities to time the run, and registers a shutdown handler to catch fatals that kill the request mid-job. A separate five-minute scan compares each event’s schedule against the clock to find misses. Runs are written to one custom table, pruned to 30 days. It does not modify, reschedule, or remove your cron events — it reads and records.
It works whether WP-Cron runs on page loads or a real system cron hits wp-cron.php, and it keeps working with DISABLE_WP_CRON set. Multisite-aware: each site gets its own table and settings, and sites created after network activation are set up automatically.
Free vs Pro
Everything above is free, on every site, with no caps — unlimited monitored jobs, full 30-day history, unlimited email alerts, and the reliability analytics.
Pro adds the alerting and integrations that teams need:

WooCommerce / Action Scheduler monitoring — success and failure of Action Scheduler jobs, plus stalled-queue detection
Slack and generic webhooks — point them at Discord, Teams, Telegram, PagerDuty, Zapier, or your own endpoint
External heartbeat — your site pings an outside monitor (Healthchecks.io, Cronitor, BetterStack, or any URL) on an interval you set, so you’re alerted even when the whole site is down. Health-aware mode signals failure when jobs break, not only when the server does.
CSV export of the full run history
Weekly summary email

Pro is $49 a year for a single site, $99 for 5, $199 for 25, and $349 for unlimited sites — with a 14-day trial that doesn’t ask for a card.
Privacy and requirements

The free plugin sends nothing anywhere. It starts in anonymous mode — no signup prompt on activation, no data to Freemius unless you opt in.
Pro contacts Freemius for license activation and updates, and sends the heartbeat ping only to the URL you enter. Both are described in Third-Party Services below.
Requires WordPress 5.8+ and PHP 7.4+. Multisite supported. Translation-ready.
Uninstall drops the log table and removes every option, transient, and scheduled event it created.

Third-Party Services
The free tier runs entirely on your server. The plugin connects to outside services only in the cases below.

Freemius (licensing, updates & opt-in). CronVitals uses Freemius, a third-party service, to handle Pro license activation, deliver Pro plugin updates, and process checkout. When you activate a Pro license or opt in, information such as your site URL, WordPress/PHP environment details, and (if you opt in) your admin email is sent to Freemius. Opt-in is optional and can be skipped; the free plugin functions without contacting Freemius until you choose to activate a license.

Service: https://freemius.com/
Terms of Service: https://freemius.com/terms/
Privacy Policy: https://freemius.com/privacy/

External heartbeat (Pro, opt-in, off by default). If you enable the heartbeat and provide a monitor URL, the plugin sends a periodic HTTP request to that URL so an outside service can alert you if your site stops responding. You choose the provider and the URL; no data beyond the ping (and, in health-aware mode, a success/fail signal) is sent. Common providers and their terms:

Healthchecks.io — https://healthchecks.io/ (terms: https://healthchecks.io/terms/, privacy: https://healthchecks.io/privacy/)
Cronitor — https://cronitor.io/ (terms: https://cronitor.io/terms, privacy: https://cronitor.io/privacy)
BetterStack — https://betterstack.com/ (terms: https://betterstack.com/terms, privacy: https://betterstack.com/privacy)

延伸相關外掛

文章
Filter
Mastodon