Monitoring Reports

Documentation

Monitoring Reports

Monitoring Reports send a weekly WordPress health summary to your inbox — built from real System Health and Logs data, so you can stay proactive with zero manual effort.

Weekly delivery — Monday at 09:00 (site timezone)
System + Logs based — built from the last 7 days
AI-enhanced (optional) — richer executive summary when AI is enabled

Overview

Monitoring Reports generate a structured weekly report from your site’s System snapshot and recent Log activity. Reports are designed to be shareable with teams and clients, and to make maintenance work visible and repeatable.

Agency tip: Forward weekly reports to clients to show ongoing maintenance value and prevent “silent” technical debt.

What the report includes

  • Executive summary — a concise explanation of current stability and what matters most.
  • Risk level + health score — a 0–100 score and a clear risk label.
  • Key risk factors — the main technical signals driving the risk level.
  • Technical overview — errors, warnings, pending updates, active plugins.
  • Recommended maintenance plan — prioritized next steps (up to 4 items).
  • Recent issues — a short view of recent log samples and activity notes.

AI vs Automatic summary

  • Automatic (no AI): the report uses structured rules to produce a reliable executive summary and maintenance plan.
  • AI-enabled: if AI is enabled and a valid OpenAI key is configured, the report can include a more human executive summary and a prioritized plan labeled as Generated by AI.

How to set up Monitoring Reports

  1. Go to All DashAI → Settings → Monitoring Reports.
  2. Enable Monitoring Reports.
  3. Set the Recipient Email and click Save Changes.
  4. Optional: click Send Test Report Now to validate delivery.

How the health score is calculated (0–100)

The report starts at 100 and applies penalties based on the last 7 days of System + Logs signals. The final score is clamped between 0 and 100.

Penalties (typical rules)

  • Recent fatal errors: −25 if fatal errors were active in the last 48 hours (highest signal).
  • Past fatal errors: −5 if fatal errors happened earlier in the week, but not in the last 48 hours.
  • Warnings present: −5 if warnings exist in the weekly log window.
  • WordPress core update available: −15.
  • Plugin updates pending: −2 per outdated plugin (capped at −25 total).
  • PHP below 8.1: −15 (infrastructure risk).
  • HTTPS inactive: −10.
  • WP_DEBUG_LOG disabled: −5 (reduced visibility).
  • File editing enabled in wp-admin: −5.
  • File modifications enabled in wp-admin: −5.
  • Disk usage high (>80%): −10.

Risk label mapping: the report also assigns a human-friendly label (Healthy/Low/Medium/Attention/Critical/Maintenance) based on the score and “recency signals” (for example, fatal errors in the last 24–48 hours elevate risk even if other areas look stable).