wyrfel

<p>LogStore can be used to log (important) data from within your plugin.<br />
It provides a simple interface to log entries and a friendly administration interface for viewing and managing the log entries.</p>
<p>While LogStore can be used to log debug output or system events, it’s main intention is to log more extensive data, such as:</p>
<ul>
<li>system emails sent your users</li>
<li>data received from remote API calls</li>
</ul>
<h3>Usage</h3>
<p>To use LogStore in your plugin, add the following line to your plugin’s ‘plugins_loaded’ callback function:</p>
<pre><code>if (class_exists('LogStore')) $this->log = new LogStore('slug', __('Title'));
</code></pre>
<ul>
<li>The ‘slug’ should be a unique identifier for your logger.</li>
<li>The ‘Title’ will be the title used in menu entries, options and page titles.</li>
</ul>
<p>Once that’s done you can then start logging your data from anywhere within your plugin by using the following:</p>
<pre><code>if (!empty($this->log)) $this->log->log(__('My log message'), $my_log_data, 'status', 'tag');
</code></pre>
<ul>
<li>‘My log message.’ is any arbitrary message to describe your log entry.</li>
<li>$my_log_data is the extended data you want to log. This can be either an array or string.</li>
<li>‘status’ is one of ‘none’, ‘ok’, ‘warn’, ‘critical’ or ‘fatal’.</li>
<li>‘tag’ can be any kind of singular tag to  further classification to your log entries.add</li>
</ul>
<p>If you use LogStore in your plugin, you should check for it’s presence in</p>
<ul>
<li>your ‘plugins_loaded’ callback</li>
<li>your plugin activation callback</li>
</ul>
<p>You should either make LogStore use optional or notify the user that they need to install LogStore for your plugin to work properly.</p>
<h3>Plugin Hooks</h3>
<p>In the following hooks, <code>*myname*</code> stands for the name with which you instanciated the LogStore class.</p>
<h4>Action Hooks</h4>
<ul>
<li><code>logstore_init-*myname*</code> – runs during the execution of WP’s <code>init</code> action hook, passes a single boolean parameter indicating if logging is active or inactive for this logger</li>
</ul>
<h4>Filter Hooks</h4>
<ul>
<li><code>logstore_new_entry-*myname*</code> – runs during the creation of a new entry, passes a single array containing all values for that entry (‘time’, ‘message’, ‘data’, ‘status’ and ‘tag’)</li>
<li><code>logstore_entry-*myname*</code> – runs before displaying an entry on screen, passes a single array containting all values for the entry (‘time’, ‘message’, ‘data’, ‘status’ and ‘tag’)</li>
<li><code>logstore_format_entry_data-*myname*</code> – runs before displaying the formatted data on screen, passes the formatted data as string</li>
</ul>
<h3>Further Notes</h3>
<p>Please note that the ‘bulk actions’ in the log viewer are currently not<br />
working.</p>


LogStore

LogStore is a 'meta' plugin that allows other plugins to log data easily.

loopj

<p>Automatically detects errors & crashes on your WordPress site using BugSnag to notify you by email, chat or issues system.</p>
<p>All websites crash from time to time, including WordPress sites! Th BugSnag Error Reporting plugin automatically detects crashes, exceptions and other errors in your WordPress PHP code as well as any errors in plugins you are using.</p>
<p>Errors are sent to your <a href="https://bugsnag.com" rel="nofollow ugc">BugSnag Dashboard</a> for you to view and debug, and we’ll also notify you by email, chat, sms or create a ticket in your issue tracking system if you use one. We’ll also show you exactly how many times each error occurred, and how many users were impacted by each crash.</p>


BugSnag Error Monitoring plugin

The plugin is easy to set up; all errors can be monitored via the Bugsnag dashboard. You can also set different log levels and differ between the environments (dev/production) of your website.

Bonus: There are lots of cool integrations like Slack (Push Notifications), GitHub (New Issues) and much more!

Easy error monitoring

Seamless integration with Bugsnag, just perfect.

Works great, people are just dumb

This plugin used to be one of the best tools out there, however, it seems like is not being maintained anymore. 

There is no support for the recent releases of PHP (8.0, 8.1). Recent support requests are not being handled anymore as well.



Abandoned.

Automatically detects errors & crashes on your WordPress site using BugSnag to notify you by email, chat or issues system.

LogStore vs BugSnag Error Monitoring plugin