Andy Whalen

Creates a log file for network/multisite super admin actions.
The following actions are logged for Super Admin users. WordPress action names are listed in parenthesis:
<ul>
<li>change network settings (update_site_option)</li>
<li>grant super admin privileges (granted_super_admin)</li>
<li>revoke super admin privileges (revoked_super_admin)</li>
<li>upgrade blog (wpmu_upgrade_site)</li>
<li>add blog (wpmu_new_blog)</li>
<li>set blog archived (archive_blog/unarchive_blog)</li>
<li>set blog deleted (make_delete_blog/make_undelete_blog)</li>
<li>set blog mature (mature_blog/unmature_blog)</li>
<li>set blog spam (make_spam_blog/make_ham_blog)</li>
<li>delete blog (delete_blog)</li>
<li>delete user (wpmu_delete_user)</li>
<li>delete user (deleted_user)</li>
<li>change other user’s settings (edit_user_profile_update) [NOTE: doesn’t show diff]</li>
<li>change blog setting (updated_option) [NOTE: may occasionally log annoyingly large diffs]</li>
</ul>
The following actions are logged for ANY user:
<ul>
<li>login (wp_login)</li>
<li>logout (wp_logout)</li>
<li>new user (user_register)</li>
</ul>
Some actions that change data will show what the value was before and after.
Below is an example of a log entry when the user ‘smith’ has changed the Network site name from “WP Local Network” to “WP Local Networks”:
<pre><code>[Tue, 03 Sep 2013 13:45:49 +0000] [smith:1] [update_site_option] [1] [site_name] [(WP Local Network)->(WP Local Networks)] [127.0.0.1] </code></pre>
Each line in the log file will roughly follow the below example. Individual actions may log slightly different information, but the DATETIME, USERNAME, USER_ID, ACTION, and IP_ADDRESS sections should always be populated.
<pre><code>[DATETIME] [USERNAME:USER_ID] [ACTION] [AFFECTED_OBJECT_ID] [DATA_TITLE_OR_KEY] [(VALUE_BEFORE)->(VALUE_AFTER)] [IP_ADDRESS] </code></pre>

Observer

Creates a log file for network/multisite super admin actions.

WP Enforcer

Keep an eye on the most important aspects of your WordPress site from one central location. Our plugin automatically sends activity that interacts with your database for things like posts, comments, authentication, and more to the cloud in realtime. This gives you peace of mind that you know what bots, spam, or other illegitimate traffic is interacting with your site.
Enable WP Enforcer to analyze your site for suspicious traffic patterns. With our vast database of IP addresses we can determine if the threat is coming from unwanted proxies, TOR network, nefarious web crawlers, or generally considered a threat to the community.
Check to see the current uptime percentage and response time of your site with 1 minute health checks. Get alerted when your site is down!
Take back control of where your traffic comes from. When using WP Enforcer you can decide to block certain traffic signatures and send them to our “safe zone”. That has been proven to help eliminate spam and malicious traffic.
Many agencies and successful WordPress users will run multiple sites. With our innovative cloud based platform we allow you to add our plugin to monitor more than one site and interact with it all from one dashboard for convenience.

Audit the activity of your site and get uptime statistics all from a central platform.

Observer vs WP Enforcer