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.

stayallive

This plugin can report PHP errors and Browser (JavaScript) errors to Sentry.
It will auto detect authenticated users and add context where possible. All context/tags can be adjusted/expanded using filters.
For more information and documentation have a look at the <a href="https://github.com/stayallive/wp-sentry/tree/v8.10.0#readme" rel="nofollow ugc">full documentation</a>.
<h3>Contributors</h3>
See: <a href="https://github.com/stayallive/wp-sentry/graphs/contributors" rel="nofollow ugc">github.com/stayallive/wp-sentry/graphs/contributors</a>

Sentry for WordPress

Perfect, this just works perfectly with zero setup. Fantastic!

Works great

WP Sentry is a great integration of Sentry for WP needs with extensive documentation which is easy to use. And in case you need it the support is great. Thanks a lot, Alex!

Great integration for WP

This plugin is fantastic. It is simple and fast, and it does exactly what it needs to, with no extra fluff.

Also, the support is top-tier. Alex responded with an immediate solution.

Simple and effective, top-support

A (unofficial) WordPress plugin to report PHP errors and Browser (JavaScript) errors to Sentry.

Custom Logging Service vs Sentry for WordPress