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.

psicosi448

End users can benefit from wp2syslog:
<ul>
<li>Log entries for core events help to keep track of the daily business, especially on multiuser blogs.</li>
<li>Log entries for core events can raise awareness for threats and problems, for example abuse attempts.</li>
<li>Log entries triggered by plugins allow the user to comprehend the functionality of the plugin.</li>
</ul>
Developers can benefit in two ways from wp2syslog:
<ul>
<li>At each point of the code, a log entry can be triggered. No need to print to the browser, just let wp2syslog put it in the database, and you can have a look later.</li>
<li>You can develop your plugins with support for wp2syslog. This will give your users the chance to better understand what your plugin is doing (see doc/specs.html).</li>
</ul>
<h3>Credits</h3>
This plugin is forked from first 0.2 version of http://www.ossec.net/wpsyslog2/ 
already forked from the wpsyslog plugin by Alex Guensche ( http://www.zirona.com/software/donate ).
The firts version of this plugin was developed during a project with the German “Menschen für Tierrechte” (Humans for Animal Rights). 
It is an organisation of activists who advocate animal rights and fight against abuse of animals. They generously decided to donate 
this work to the general public by letting Zirona put it under the GNU GPL and allowing us to promote and distribute it.
Please support the work of Humans for Animal Rights, e.g. by placing a link to <a href="http://www.tierrechte.de/" title="www.tierrechte.de" rel="nofollow ugc">Humans for Animal Rights</a> and 
spreading the word. Not (only) because of this plugin, but generally for a better treatment of the beings on this planet.

wp2syslog

wp2syslog -- Global logging facility for WordPress (WPsyslog revisited)

Custom Logging Service vs wp2syslog