ccprog

This plugin is derived from the no longer supported 
<a href="https://wordpress.org/plugins/wordpress-logging-service" rel="ugc">WordPress Logging Service</a>. 
Despite that it is not compatiple with it, and there is no upgrade path from one 
to the other.
<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>
Check to test if the plugin is active:
<pre><code>CLGS = true
</code></pre>
Defined severity levels:
<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>
returns <code>true</code> if <code>$category</code> is registered.
<pre><code>clgs_register ( $category, $description )
</code></pre>
registers <code>$category</code> as a log category. <code>$description</code> will be shown in the 
management page. 
It is good practice to use unique categories for each plugin that publishes 
log messages.
<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 
 wp_kses_data)</li>
</ul>
returns <code>false</code> if the category is already registered or it is too long.
<pre><code>clgs_clear ( $category )
</code></pre>
deletes all log entries of <code>$category</code>.
<ul>
<li><code>string $description</code> existing category</li>
</ul>
returns number of deleted entries or <code>false</code> if action failed.
<pre><code>clgs_unregister( $category );
</code></pre>
deletes all log entries and then removes <code>$category</code>.
<ul>
<li><code>string $description</code> existing category</li>
</ul>
returns <code>false</code> if false if action failed.
<pre><code>clgs_log( $category, $text, $severity = null, $user = null, $blog_id = null, $date = null );
</code></pre>
writes a new log entry in the specified category
<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 
by <code>wp_kses_data</code>)</li>
<li><code>int $severity</code> one of defined severity levels (see above); if missing defaults to 
 CLGS_NOCATEGORY</li>
<li><code>int | string | WP_User $user</code> user id, slug or WP user object are aceptable; if missing 
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>; 
if missing defaults to current time</li>
</ul>
returns <code>false</code> if entering the log failed.

Custom Logging Service

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

Dmitri Martin

Traffic Monitor gives you full visibility into how people and bots are hitting your site.
Unlike bloated analytics and security plugins, Traffic Monitor focuses on logging raw request data that you control. You’ll know which pages are cached, which bots are visiting, where users are coming from, and how many requests are tied to each IP/browser combination.
Perfect for developers, marketers, and site owners who want fast insights—without handing over their traffic data.
<h3>What Makes It Different</h3>
<ul>
<li>✅ Logs requests for both cached and non-cached pages</li>
<li>✅ Lets you export raw traffic logs as raw CSV for your own analysis</li>
<li>✅ Identifies repeat ad clicks for spotting potential click fraud</li>
<li>✅ Reveals which bots are hitting your site, so you can block them elsewhere (example: Cloudflare)</li>
<li>✅ Tracks IP address, fingerprint, device type, cache status, response code, and more</li>
<li>✅ Displays referrer URLs and query strings</li>
<li>✅ Records the original source of requests by the same visitor as they surf your website</li>
<li>✅ Doesn’t auto-block or inject junk—just clean, useful data</li>
<li>✅ Works great with Cloudflare, caching plugins, and reverse proxies</li>
</ul>
<h3>Key Features</h3>
<ul>
<li>Logs every page request, including IP address, referrer, user-agent, browser, device, method, and more.</li>
<li>Detects cached traffic even if served by Cloudflare, your web host, or a plugin.</li>
<li>Identifies bot traffic by bot name and category.</li>
<li>View click IDs like gclid and fbclid from ad platforms like Google and Meta.</li>
<li>Records repeat ad clicks to detect potential click fraud.</li>
<li>Bulk delete or export logs with one click.</li>
<li>Search, sort, and drill into data from your dashboard.</li>
<li>Built-in help tabs with definitions, setup help, and troubleshooting.</li>
</ul>
<h3>Use Cases</h3>
<ul>
<li>Debug integrations instantly: Know exactly what URLs are being hit, by which devices, and with what parameters. No guesswork.</li>
<li>Spot caching gaps: See which pages are served from cache and which aren’t, even with Cloudflare or plugin-level caching.</li>
<li>Understand real-world traffic: Track entry pages, referrers, devices, and browsers—whether human or bot.</li>
<li>Catch click fraud signals: Identify repeat ad clicks tied to the same IP/user agent fingerprint or session, even if served from cache.</li>
<li>Audit referrers: View exactly which websites or campaigns are driving traffic (including query strings).</li>
<li>Filter out noise: Use bot labels and device types to focus only on human traffic when analyzing patterns.</li>
</ul>

Traffic Monitor

Lightweight traffic logger for WordPress analytics. View, filter, and export page request data; monitor caching; detect bots; and spot click fraud.

Custom Logging Service vs Traffic Monitor