SuccessMedia

LogMouse monitors errors and system resources in your CMS system. Notifications are automatically sent for E_XXXX errors, and the Pro version provides additional notification channels and advanced system resource monitoring for professional users.
<h3>⭐️Features of the Free Version:</h3>
<ul>
<li>Email notifications: Automatically sends notifications for E_XXXX errors.</li>
<li>Configurable error tracking: Select which errors should trigger notifications.</li>
<li>Test functionality: Generate a test error with a button to check your configuration.</li>
<li>Enable or disable notifications: Manage notifications as needed.</li>
</ul>
<h3>🔥Additional Features of the Pro Version:</h3>
<ul>
<li>
Additional Tools:
<ul>
<li>Resend error Messages</li>
<li>Error Log</li>
<li>Remote Dashboard (coming soon)</li>
</ul>
</li>
<li>
Advanced notification channels:
<ul>
<li>Slack</li>
<li>MS Teams</li>
<li>Telegram</li>
<li>WebHooks</li>
<li>Pagerduty (coming soon)</li>
</ul>
</li>
<li>
Comprehensive system resource monitoring:
<ul>
<li>Database:</li>
<li>Slow Queries</li>
<li>Threads Connected</li>
<li>Table Size</li>
<li>Memory:</li>
<li>Total</li>
<li>Used</li>
<li>Peak</li>
<li>% Used</li>
</ul>
</li>
</ul>
Upgrade 🚀 to the Pro version to gain full control and visibility of your system! 
<a href="https://logmouse.com/upgrade" rel="nofollow ugc">Upgrade Now</a>
<h3>How to Start</h3>
Once the plugin is activated: 
1. Go to Logmouse > Settings to configure and verify the receiver email. 
2. Select the errors you want to monitor. 
3. Set Monitoring to Active 
4. Click ‘Trigger Error’ Button and Check the Inbox 
5. Ready to Monitor.
For more detailed instructions, refer to the online <a href="https://logmouse.com/user-doc" rel="nofollow ugc">documentation</a>.
<a href="https://buy.stripe.com/3csdTnbBbd6wesM8wE" rel="nofollow ugc">Donate</a>

LogMouse – Error Monitoring

Professional Error Monitoring, Reporting and System Resource Tracking for your CMS.

Weston Ruter

Felix Arntz

Google

As <a href="https://developers.google.com/web/updates/2018/09/reportingapi" rel="nofollow ugc">noted on the Google Developers blog</a>:
<blockquote>
The Reporting API defines a new HTTP header, <code>Report-To</code>, that gives web developers a way to specify server endpoints for the browser to send warnings and errors to. Browser-generated warnings like CSP violations, Feature Policy violations, deprecations, browser interventions, and network errors are some of the things that can be collected using the Reporting API.
</blockquote>
This plugin provides a storage mechanism and endpoint for browser reports according to the Reporting API spec in WordPress, as well as an admin interface for browsing these reports. It also provides an API for sending the <code>Report-To</code> response headers.
As the Reporting API specification is still evolving and at an early stage, the plugin reflects that and is currently an experimental prototype, to demonstrate how Reporting API can be used in WordPress.
<h4>Did you know?</h4>
There is also a new specification called Feature Policy which will integrate with the Reporting API specification. There is a <a href="https://wordpress.org/plugins/feature-policy/" rel="ugc">WordPress plugin for Feature Policy</a> as well.

Reporting API

WordPress plugin for receiving browser reports via a Reporting API endpoint.

LogMouse – Error Monitoring vs Reporting API