What the admin Event Log is #
The admin Event Log is a record of diagnostic events the Loupely WordPress Plugin has captured from your site, stored in your WordPress Database and viewable from your WordPress Admin dashboard. It’s not a real-time monitor and it’s not a replacement for running a diagnosis. It’s a timestamped log of what the plugin has seen during past capture sessions.
Find it at Loupely > Event Log in your WordPress Admin sidebar.
What the log shows #
Each entry in the Event Log represents 1 capture session. For each entry you’ll see:
- the date and time of the capture
- the URL of the page that was captured
- the type of event detected (PHP error, JavaScript error, WooCommerce pipeline event, Hook Execution data, and so on)
- whether a diagnosis was generated from this capture
- the failure class if a diagnosis was produced
The log doesn’t show the full capture file contents or the diagnosis text. Those are generated at the time of the capture and are available in the Chrome extension popup. The log is a reference record, not a replayable diagnostic session.
When the Event Log is useful #
Tracking recurring failures. If a problem is intermittent, the Event Log lets you see whether Loupely has captured evidence of it during previous sessions, even if you weren’t watching when it happened. A pattern of PHP Errors in the same plugin file appearing across multiple capture sessions is more informative than a single instance.
Confirming a fix worked. After you act on a triage recommendation, running a new capture and checking the Event Log can confirm that the event that was causing the failure is no longer appearing.
Providing context to a developer. If you’re handing a problem to a developer, the Event Log gives them a broader picture of the site’s failure history beyond the single most recent capture.
Event Log retention #
Events in the log are automatically deleted after the retention period configured on the plugin settings page. The default is 30 days. Older events are pruned automatically to keep the database size manageable. If you need to keep a record of a specific set of events beyond the retention window, export or copy the relevant entries before they’re pruned.
You can also manually clear the Event Log from the settings page if you want to start fresh, for example after resolving a persistent issue and wanting a clean baseline going forward.
What the Event Log is not #
The Event Log is not a continuous server monitor. It only records events from capture sessions you triggered using the Chrome extension. It won’t show you errors that happened while you were away from your site, overnight, or in sessions where you didn’t run a diagnosis. If you want continuous monitoring of your WordPress error log, that’s a separate tool (your hosting provider’s log viewer, or a dedicated monitoring plugin). Loupely’s Event Log is specifically a record of what the diagnostic system found during your diagnostic sessions.