stasionok

Incoming Hook Logger is designed for developers who need to debug or monitor incoming webhook requests sent to their WordPress site. It captures all request data without interrupting the original request flow, allowing other plugins to process the webhooks as usual.
<h3>Key Features:</h3>
<ul>
<li>Multiple URLs: Specify one or more URLs (or partial URLs) to monitor.</li>
<li>Full Data Capture: Logs request method, full URL, headers, raw body, and sender’s IP.</li>
<li>Admin Interface: View logs directly in the WordPress dashboard with two tabs (Settings and Logs).</li>
<li>Filtering & Search: Easily find specific entries by filtering by URL or searching through body and headers.</li>
<li>Secure Storage: Logs are stored in a dedicated database table (<code>wp_webhook_logs</code>) and accessible only to administrators.</li>
</ul>

Incoming Hook Logger

Log incoming webhooks (URL, headers, body, IP). View, filter, and search in the WordPress admin without blocking other plugins.

Shash

Track and receive notifications for who logged in, who changed the theme, who activated/deactivated a plugin, failed login attempts, password requests, etc.
Note: This plugin required a operational.co account. Operational is a SaaS Event tracker tool for tech products.
Why use this?
<ul>
<li>Event logs are stored on external servers. If your website goes down, your logs don’t go down.</li>
<li>With existing WordPress activity log plugins, they add logs in your WordPress website, which might slow down your website</li>
<li>Unlike WordPress activity log plugins, you can receive mobile notifications for your activity logs.</li>
</ul>

Incoming Hook Logger vs Operational