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.

bitcoinapi

PermaLogger is a comprehensive WordPress activity logging plugin that tracks user actions and system events in your WordPress admin area. All events are logged locally and can be synced to the PermaLogger external service for immutable storage and analysis using blockchain technology.
<h4>Features</h4>
<ul>
<li>User Login Tracking – Monitor successful and failed login attempts</li>
<li>Profile Updates – Track changes to user profiles including password changes</li>
<li>Email Changes – Log when users update their email addresses</li>
<li>Dashboard Movement – Track page navigation within the WordPress admin</li>
<li>Post & Page Tracking – Monitor creation, updates, deletions, and status changes</li>
<li>Content Diff Tracking – Optional git-style diffs showing exact content changes</li>
<li>Admin Hooks – Comprehensive tracking of all WordPress admin hooks (optional)</li>
<li>Local Database Storage – All logs stored in your WordPress database</li>
<li>API Sync – Automatic syncing to external PermaLogger service</li>
<li>Log Viewer – Built-in interface to view and filter logs</li>
<li>Pagination & Filtering – Easy navigation through your activity logs</li>
</ul>
<h4>Use Cases</h4>
<ul>
<li>Security auditing and compliance</li>
<li>Debugging user-reported issues</li>
<li>Monitoring content changes</li>
<li>Tracking admin activity</li>
<li>Compliance with data regulations</li>
</ul>
<h4>Privacy & Data</h4>
PermaLogger logs user actions including usernames, IP addresses, and timestamps. The plugin can sync this data to an external service (PermaLogger.com) if you provide an API key. You should inform your users about this tracking in your privacy policy.
<h4>Requirements</h4>
<ul>
<li>WordPress 5.0 or higher</li>
<li>PHP 7.0 or higher</li>
<li>bitcoinapi.io API key (get one at https://bitcoinapi.io)</li>
</ul>
<h3>External Services</h3>
This plugin connects to the BitcoinAPI external service to sync and store WordPress activity logs. This connection is required for the plugin’s core functionality of providing immutable, blockchain-based log storage.
What is sent: 
* User activity data including usernames, user IDs, email addresses, IP addresses 
* Timestamps of actions performed 
* Details of WordPress actions (login attempts, profile updates, email changes, page/post modifications, admin navigation, etc.) 
* Request data associated with tracked events
When is data sent: 
* Data is sent automatically when the temporary log file reaches 100KB in size 
* Each batch contains all logged events since the last sync 
* Syncing only occurs if you have provided a valid API key
Service Information: 
* Service Provider: BitcoinAPI 
* Service Used: Log Storage and Blockchain Timestamping 
* API Endpoint: https://bitcoinapi.io/api/ 
* Terms of Service: https://bitcoinapi.io/terms 
* Privacy Policy: https://bitcoinapi.io/privacy
Important Notes: 
* All logs are stored locally in your WordPress database regardless of API sync status 
* You must provide a valid API key from https://bitcoinapi.io for external syncing to occur 
* Without an API key, the plugin will still log events locally but will not sync externally 
* Users should be informed about this data transmission in your site’s privacy policy
<h3>Privacy Policy</h3>
PermaLogger logs user activity on your WordPress site. The following data is collected:
<ul>
<li>Username and user ID</li>
<li>Email address</li>
<li>IP address</li>
<li>Timestamp of actions</li>
<li>Details of actions performed (page visits, content changes, etc.)</li>
</ul>
If you provide an API key, this data is transmitted to BitcoinAPI external service via HTTPS (bitcoinapi.io). Make sure to disclose this data collection in your site’s privacy policy and obtain necessary user consent.
<h3>Support</h3>
For support, feature requests, or bug reports, please visit: 
* Plugin Support Forum: (will be available after plugin approval) 
* Documentation: https://bitcoinapi.io/docs 
* Website: https://bitcoinapi.io 
* Contact: support@bitcoinapi.io
<h3>Credits</h3>
Developed by BitcoinAPI 
https://bitcoinapi.io

PermaLogger

Track all hookable actions in the WP-Admin area and log them to PermaLogger's external service for comprehensive activity monitoring.

Observer vs PermaLogger