ccprog

<p>This plugin is derived from the no longer supported<br />
<a href="https://wordpress.org/plugins/wordpress-logging-service" rel="ugc">WordPress Logging Service</a>.<br />
Despite that it is not compatiple with it, and there is no upgrade path from one<br />
to the other.</p>
<h4>Features</h4>
<ul>
<li>No log entries generated by the plugin itself, all come from external API calls</li>
<li>Organisation of log entries in freetext categories</li>
<li>Severity levels</li>
<li>Freetext log messages</li>
<li>Entries can be marked as seen and then filtered from being displayed again</li>
<li>Filtering by minimum severity level</li>
<li>Sort by date, category, user name, severity or blog name (in Multisite installations)</li>
<li>Access to the log page can be granted by user role</li>
</ul>
<h3>API</h3>
<h4>Constants</h4>
<p>Check to test if the plugin is active:</p>
<pre><code>CLGS = true
</code></pre>
<p>Defined severity levels:</p>
<pre><code>CLGS_NOSEVERITY = 0
CLGS_INFO = 1
CLGS_NOTICE = 2
CLGS_WARNING = 3
CLGS_ERROR = 4
CLGS_FATALERROR = 5
</code></pre>
<h4>Functions</h4>
<pre><code>clgs_is_registered ( $category )
</code></pre>
<ul>
<li><code>string $category</code></li>
</ul>
<p><em>returns</em> <code>true</code> if <code>$category</code> is registered.</p>
<pre><code>clgs_register ( $category, $description )
</code></pre>
<p>registers <code>$category</code> as a log category. <code>$description</code> will be shown in the<br />
management page.<br />
It is good practice to use unique categories for each plugin that publishes<br />
log messages.</p>
<ul>
<li><code>string $category</code> At most 190 (unicode) characters</li>
<li><code>string $description</code> can contain HTML same as comments (filtered by<br />
  wp_kses_data)</li>
</ul>
<p><em>returns</em> <code>false</code> if the category is already registered or it is too long.</p>
<pre><code>clgs_clear ( $category )
</code></pre>
<p>deletes all log entries of <code>$category</code>.</p>
<ul>
<li><code>string $description</code> existing category</li>
</ul>
<p><em>returns</em> number of deleted entries or <code>false</code> if action failed.</p>
<pre><code>clgs_unregister( $category );
</code></pre>
<p>deletes all log entries and then removes <code>$category</code>.</p>
<ul>
<li><code>string $description</code> existing category</li>
</ul>
<p><em>returns</em> <code>false</code> if false if action failed.</p>
<pre><code>clgs_log( $category, $text, $severity = null, $user = null, $blog_id = null, $date = null );
</code></pre>
<p>writes a new log entry in the specified category</p>
<ul>
<li><code>string $description</code> a registered category name</li>
<li><code>string $text</code> the logged message, can contain HTML same as comments (filtered<br />
by <code>wp_kses_data</code>)</li>
<li><code>int $severity</code> one of defined severity levels (see above); if missing defaults to<br />
  CLGS_NOCATEGORY</li>
<li><code>int | string | WP_User $user</code> user id, slug or WP user object are aceptable; if missing<br />
defaults to current user (or a placeholder if none is logged in)</li>
<li><code>int $blog_id</code> blog id; if missing defaults to current blog</li>
<li><code>int | double | string $date</code> a UNIX timestamp or a string recognized by <code>strtotime()</code>;<br />
if missing defaults to current time</li>
</ul>
<p><em>returns</em> <code>false</code> if entering the log failed.</p>


Custom Logging Service

Provides a simple API for storing miscellaneous log entries and displays them in a Dashboard subpage.

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.

Custom Logging Service vs Plainview Activity Monitor