All Modules FREE & PRO

Error Log Aggregation

Parses your WordPress PHP error log and groups recurring issues by severity — so you stop scrolling raw log files and start fixing what actually matters.

  • Grouped By Severity
  • 0 Database Writes
  • Read-Only Architecture

What This Module Does

Raw PHP error logs are noisy. A single broken function call can generate thousands of identical lines, drowning out the critical errors that actually need attention. The Error Log Aggregation module parses your WordPress PHP error log, deduplicates repeating entries, groups everything by severity category, and surfaces the most impactful issues at the top — so a 50,000-line log file becomes a short, actionable list in seconds.

Features at a Glance

Severity-Grouped WordPress Error View

Errors are grouped into three categories: Critical (fatal errors, exceptions, database errors), Performance (slow query warnings, timeout notices), and Informational (deprecated function calls, notices, warnings). Focus immediately on what's actually breaking your WordPress site.

Occurrence Count Deduplication

Repeating identical WordPress PHP errors are collapsed into a single entry with an occurrence count. A function that fails on every page load shows once with a count of 10,000 — not 10,000 lines hiding the three genuinely unique errors.

Top Critical Errors at a Glance

The most frequently occurring critical-severity WordPress errors surface at the top of the report, making it immediately obvious where to focus attention when auditing any site.

WordPress Log File Location & Metadata

Reports the path to the active PHP error log, its size, last modified timestamp, and total entry count — confirming WordPress error logging is active and you're reading the right file.

Read-Only — Never Clears the WordPress Log

The module reads the log file only — it never writes to it, clears it, rotates it, or modifies it in any way. Completely safe to use on production WordPress sites.

Why It Matters

  • Turn a 50,000-line WordPress PHP error log into a five-item action list in seconds
  • Identify the single most common error on any WordPress site before spending hours debugging
  • Distinguish between noisy-but-harmless deprecated notices and genuine WordPress fatal errors
  • Verify that WordPress PHP error logging is actually active and writing to the expected location
  • Audit a client WordPress site's complete error history without downloading any log files

Frequently Asked Questions

Does WP Health Inspector need WP_DEBUG enabled to read the WordPress error log?

No. The module reads the error log path from PHP's error_log ini directive, regardless of WordPress debug settings. As long as PHP is configured to write errors to a log file, the module can read it.

What if my WordPress PHP error log is very large?

The module reads the log in chunks and processes a maximum number of lines to prevent memory exhaustion. Very large logs are sampled from the most recent entries, and the module notes when the log has been truncated for performance.

Can it read WordPress error logs stored in custom paths?

The module reads from the path returned by ini_get('error_log'). If PHP is configured to write to a custom path, the module reads from that path as long as the web server process has read permission.

Is this available in the free Lite version?

Yes — the full Error Log Aggregation module is available in both Lite and Pro.

Find the Real WordPress Errors — Not the Noise

Turn your WordPress PHP error log into an actionable priority list — included in the free Lite version.

Already Included in Lite — Free

Error Log Aggregation is fully available in the free Lite version — install it and get your first log analysis immediately.

Download Lite — Free

Also Included in Pro

Pro includes Error Log Aggregation alongside all seventeen diagnostic modules and eight Pro-exclusive deep inspections.

Get Pro Now