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.

mrdenny

Allows for more details reporting for the “Redirection” plugin by John Godley. 
This plugin will not do anything for you without using the Redirection plugin 
to handle your 301 redirections. This plugin was built to fix a gap in the 
reporting which the Redirection plugin has.

Redirection Reporting

Allows for daily reporting for redirected requests.

Reporting API vs Redirection Reporting