Miterl Connect: WordPress Plugin Guide for Maintenance Teams

Three Moments Where WordPress Monitoring Breaks

External uptime monitoring does a clean job on server and network outages. What it does not see is what happens inside WordPress itself. Three failure modes show up in every WordPress maintenance operation eventually:

1. False DOWN alerts during updates — the moment a core, plugin, or theme update starts, responses briefly stop and external uptime checks register a DOWN event
2. WP-Cron going silent — WordPress's pseudo-cron only fires when a visitor arrives; on low-traffic sites, scheduled posts, backups, and auto-updates quietly stop, with no TTFB symptom
3. Update backlog building up — outdated core, plugin, and theme versions pile up vulnerability risk long before any external signal fires

The first two are invisible from outside the server, by design. The third is invisible until something breaks. None of the three is solved by adding more external probes. Background on how external monitoring fits into WordPress maintenance is in "How to Add Uptime Monitoring to WordPress Maintenance Plans."

What Miterl Connect Handles on the Inside

Miterl Connect is the official Miterl plugin for WordPress sites. It bundles the three capabilities that monitor the inside of WordPress and ships them as one plugin. Miterl Connect is a complement to external monitoring, not a replacement — both run side by side.

1. Auto maintenance window during WordPress updates

The instant a WordPress core, plugin, or theme update starts, the plugin tells Miterl to open a one-hour maintenance window automatically and close it the moment the update finishes. No deploy script, no human at the keyboard, no Webhook to remember. WordPress sites with auto-updates enabled — and most production sites that ship security patches automatically do — get the same noise reduction as ones managed by a deploy pipeline.

2. wp-cron heartbeat every 5 minutes

The plugin sends a heartbeat from inside WordPress to a Miterl Heartbeat monitor every 5 minutes, as long as wp-cron is alive. A 15-minute silence triggers an alert. Sites running DISABLE_WP_CRON with a system cron still send the heartbeat — as long as WordPress's scheduled events actually run, the signal keeps flowing, which makes it a live check that your schedule is really executing.

3. Daily digest of pending updates

Pending core, plugin, and theme versions are pushed to the Miterl monitor detail view once a day (and again right after an update finishes). The list is visible on every plan, including Free. Backlog left pending for 7 days or more triggers an email — that escalation is the only part gated to Standard plans and above.

Full configuration is in the Miterl documentation. The plugin zip ships from miterl.com/dl/miterl-connect.zip — not yet on wordpress.org; distributed directly by us.

Field Test: Updating Akismet 5.7.1 to 5.7.2

On 2026-09-13, the day of release, we ran a manual field test on an internal WordPress 7.1 + PHP 8.4 staging environment (URL not published).

Setup: Akismet was downgraded to 5.7.1, then brought back to 5.7.2 with wp plugin update akismet. The actual update takes a few seconds.

What Miterl recorded:

• Maintenance auto-window: at 16:34, Miterl's audit log recorded a maintenance start (one-hour window) — and the same minute recorded the maintenance end. The window opened and closed inside the same minute
• Update digest: the monitor detail view showed one pending update (Akismet 5.7.1 → 5.7.2) before the update, then "0 pending / all up to date" once the post-update inventory resync landed
• Heartbeat: wp-cron was alive throughout the test, and the … (wp-cron) Heartbeat monitor in Miterl stayed UP for the whole 30-minute observation window

The non-obvious finding: on a low-traffic WordPress site, wp-cron only fires when someone visits. Miterl's external HTTP monitor, by pinging the site every 5 minutes, ends up triggering wp-cron as a side effect. External monitoring and the plugin end up supporting each other — exactly the complement relationship we wanted. Sites that already moved to a system cron with DISABLE_WP_CRON are unaffected.

Setup: One Connection Key, Two Steps

The setup is the same whether you run one WordPress site or fifty. A connection key belongs to one monitor (= one site); agencies running multiple sites issue one key per site and never share keys across sites.

1. Issue the connection key in Miterl

1. Sign in to Miterl, open the WordPress site's monitor, switch to the Operations tab
2. Open the WordPress integration card and click Issue connection key. Copy the mc_… key

2. Install the plugin

Download the WordPress plugin zip, then upload it through WordPress admin → Plugins → Add New → Upload Plugin. With wp-cli, a single command is enough:

wp plugin install https://miterl.com/dl/miterl-connect.zip --activate

After activation, WordPress admin → Settings → Miterl Connect shows the connection key field. Paste the mc_… key from step 1, click Save. Once the first request arrives, the card on the monitor detail view shows Connected and the Heartbeat and inventory data start flowing. Note that issuing a key also auto-creates a Heartbeat monitor for wp-cron, so one WordPress site uses two monitors (HTTP + Heartbeat) — Free allows 5 monitors, Standard 100.

3. Pairing with system cron on DISABLE_WP_CRON sites

On sites with define('DISABLE_WP_CRON', true); in wp-config.php, add a system cron entry so wp-cron runs on a schedule instead of piggybacking on visitor traffic:

*/5 * * * * curl -s https://example.com/wp-cron.php?doing_wp_cron=1 > /dev/null 2>&1

Miterl Connect's Heartbeat keeps working with this configuration, because the system cron is what runs wp-cron. If you don't want heartbeat alerts at all, pause the auto-created Heartbeat monitor in Miterl — the maintenance auto-window and the daily backlog digest continue to function.

How Miterl Connect Complements External Monitoring

The recurring theme in the web agency use case is that Miterl Connect is a complement, not a replacement, for external monitoring.

A single plugin cannot replace external monitoring. When the server itself fails, the plugin goes down with it and simply stops sending. The recommended setup runs both layers in parallel. The fact that the external HTTP probe itself triggers wp-cron is a useful side effect of running them together, not a substitute for either.

Folding Miterl Connect Into a 30-Client Retainer

Agencies running 30+ WordPress retainers benefit from a repeatable setup pattern. Three design choices that have held up in production:

1. Attach the connection key to the site's main HTTP monitor. A key belongs to exactly one monitor, so pick the uptime monitor for that site; SSL or keyword monitors on the same site don't need their own key. Keys are cheap to revoke and reissue — reissue in Miterl, paste the new key into the plugin, and the old one is dead the moment you reissue
2. Treat the plugin as part of onboarding, not as an option. New sites get Miterl Connect at the same time as their first monitor. Skipping it now means revisiting after the first false alert
3. Surface "0 pending updates" in monthly client reports. The pending list on the monitor detail view lets you show that updates are not being left to pile up — a maintenance outcome clients can actually see

Miterl Connect itself has no extra charge — it lives inside your plan's monitor quota. The full retainer playbook with pricing and white-label positioning is in the web agency use case.

Summary and Next Steps

Miterl Connect is the official Miterl plugin for WordPress sites. It covers the three failure modes external monitoring cannot see: false DOWN alerts during updates, wp-cron going silent, and update backlog building up. The plugin is designed to run alongside external monitoring — both layers feed the same Miterl workspace.

Field testing on 2026-09-13 confirmed the three core paths: Akismet 5.7.1 → 5.7.2 triggered an auto maintenance window (open and close recorded in the same minute at 16:34), the monitor detail view updated from pending: 1 to pending: 0 after the inventory resync, and the wp-cron Heartbeat stayed UP throughout the observation window. Connection keys and Heartbeat work on the Free plan; the daily backlog email is gated to Standard and above.

• Try it now: Sign up for Miterl (Free plan can issue connection keys)
• Setup walkthrough: Miterl documentation / WordPress integration
• Download: miterl-connect.zip
• Operational patterns: Web agency 30-client retainer use case

If you already run external monitoring on a WordPress site, one connection key adds the layer that external monitors could never see.