Mikhail Alferov

Error notifications help to immediately identify the causes of failures and quickly fix bugs so that the site runs smoothly and the business does not lose customers due to hidden errors.
If you are a developer, install the plugin to find out about specific errors or all errors in the PHP code, even if the error occurred in an unexpected place that could not be foreseen in advance.
The plugin allows you to configure the types of errors that you want to receive notifications about. Uncaught exceptions won’t break your site — they’re logged and made available for centralized custom handling via the <code>enot_exception_handler_should_exit</code> filter. Only real fatal errors stop the script, but you’ll still get full error details.
The notification will contain the type of error, the file name, and the line number where the error occurred or an uncaught exception was thrown, as well as a callback stack trace.
If you are the site owner, after installing the plugin, specify the email address of the developer who maintains the site in the plugin settings so that the plugin can start detecting and sending messages to the developer about serious errors that cause the business to lose orders or customers.
A notification with detailed information about the causes of the error will indicate to the programmer which plugin or theme caused the failure (which often goes unnoticed for a long time with automatic updates of plugins or themes), and the developer will fix the error before the failure is reported to customers.
It also helps to find out about critical errors even without access to the server logs or WordPress dashboard.
Note: The errors named *_NOTICE or *_WARNING are not too severe, but with others, the site breaks down and the user gets a negative experience.
<h4>Features</h4>
<ul>
<li>Customizable PHP error levels</li>
<li>Catch unhandled exceptions from try-catch blocks</li>
<li>Log stack traces, errors from @ operator, and JavaScript errors (Premium only)</li>
<li>Display user-friendly messages for critical PHP errors</li>
<li>Configurable email address for notifications</li>
<li>Multilingual support: RU, EN</li>
<li>Free updates to new versions (Premium only)</li>
<li>Error notifications via email</li>
<li>Error notifications via Telegram (Premium only)</li>
<li>JavaScript error alerts (Premium only)</li>
<li>Database error alerts (Premium only)</li>
</ul>

Error Monitor & Notifier

Receive notifications with details when PHP errors occur on your WordPress site.

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.

Error Monitor & Notifier vs Reporting API