wakamin

<p>Write log for debugging WordPress site.</p>
<h3>How to Use?</h3>
<p>Use this function to write log.</p>
<pre><code>// Variable value can be string, array, or object
$variable = 'Variable value';

// Log file will be in /wp-content/plugins/samudra-log/log/sd_log.log
sd_log($variable);

// Log file will be in /wp-content/plugins/samudra-log/log/my-file.log
sd_log($variable, 'my-file');
</code></pre>
<h3>Restrict direct access to log file</h3>
<p>If you are using Nginx, put this code inside your server block.</p>
<pre><code>location ~ /wp-content/plugins/samudra-log/log/.*\.log$ {
    deny all;
    return 404;
}
</code></pre>


Samudra Log

edward_plainview

<p>Activity Monitor tracks all user activity on your blog or network. The activities can be viewed in global table showing activities on the whole network, or locally for just the blog you are currently viewing. The activites can be filtered so that only specific blogs / hooks / IPs / users are displayed.</p>
<p>Monitored actions include (not exhaustive):</p>
<ul>
<li>Comments: approve, held, spam, delete</li>
<li>Custom Post Types:  draft, publish, update, trash, delete</li>
<li>Logins: login, login failed, logout</li>
<li>Pageviews: admin, front-end</li>
<li>Passwords: reset, retrieve</li>
<li>Plugins: activate, deactivate</li>
<li>Pages: draft, publish, update, trash, delete</li>
<li>Posts: draft, publish, update, trash, delete, password</li>
<li>Taxonomies: create, edit, delete</li>
<li>Themes: switched</li>
<li>Updates: WordPress core, plugins, themes</li>
<li>Users: register, delete, profile changes</li>
<li>And more….</li>
</ul>
<p>The logged information consists of:</p>
<ul>
<li>A description of what was logged</li>
<li>Blog</li>
<li>Timestamp</li>
<li>Hook that was triggered</li>
<li>User ID</li>
</ul>
<h4>git</h4>
<p>The <a href="https://bitbucket.org/edward_electric/activity-monitor" rel="nofollow ugc">Activity Monitor has a git repository</a>.</p>
<h4>Security tips</h4>
<p>There are several ways for people to break in to your WordPress installation, or cause trouble by DDOS. Here are some tips on how to use the Activity Monitor and its plugins to help detect problems:</p>
<ul>
<li>Get a DDOS protection service with an API. There is a plugin to ban IPs via CloudFlare (<em>Send To CloudFlare</em>). Other APIs could be supported as the need arises.</li>
<li>If you have another DDOS service, write a script that can ban visitors by IP. Use this script with the <em>Send To Exec</em> plugin.</li>
<li>If you can’t ban users using a script, at least set up the <em>Send To E-mail</em> plugin to inform you of suspicious activity.</li>
<li>Use the Bruteforce Detect plugin to detect when an IP or IPs are trying to guess the admin’s password. Ban the IPs automatically using <em>Send To Exec</em>.</li>
<li>Do not use admin as the username for your administrator account. Instead, use some else and add the admin username to the list of banned usernames in the <em>Login Failed Username</em> plugin. Ban the IPs that cause the plugin to react.</li>
</ul>
<h4>Custom hooks</h4>
<p>See the <a href="https://pvactivitymonitor.com/doc/dev/" rel="nofollow ugc">developer documentation</a> for relevant info on how to create custom hooks.</p>


Plainview Activity Monitor

Real-time monitoring of users, content, functionality, appearance, security, and updates.

Samudra Log vs Plainview Activity Monitor