Pro: error history

The free log viewer shows the current tail of your logs. Log files rotate and get truncated, so “when did this start?” is often unanswerable. Error history fixes that: Pro keeps every captured fatal in a database you can search.

What you get

A new History tab in the log viewer, backed by a database table. Each distinct error is grouped, so you see:

• the message and its file:line,
• how many times it’s happened (count),
• when it was first seen and last seen.

Search by text, filter by type or date range, and page through the results. It’s the difference between “there’s an error right now” and “this error started six days ago, right after that plugin auto-updated.”

Retention

Under the History settings you can set how long to keep records (in days). A daily job prunes anything older automatically. Set it to 0 to keep everything.

Why it matters

Most fatal errors aren’t random — they start at a specific moment: a plugin update, a PHP version bump, a deploy. History gives you the timeline to correlate the error with the change that caused it. It’s also what powers AI access — an assistant can only tell you “your most recurring error this week” because the history is there to query.

Free vs Pro