psicosi448

End users can benefit from wp2syslog:
<ul>
<li>Log entries for core events help to keep track of the daily business, especially on multiuser blogs.</li>
<li>Log entries for core events can raise awareness for threats and problems, for example abuse attempts.</li>
<li>Log entries triggered by plugins allow the user to comprehend the functionality of the plugin.</li>
</ul>
Developers can benefit in two ways from wp2syslog:
<ul>
<li>At each point of the code, a log entry can be triggered. No need to print to the browser, just let wp2syslog put it in the database, and you can have a look later.</li>
<li>You can develop your plugins with support for wp2syslog. This will give your users the chance to better understand what your plugin is doing (see doc/specs.html).</li>
</ul>
<h3>Credits</h3>
This plugin is forked from first 0.2 version of http://www.ossec.net/wpsyslog2/ 
already forked from the wpsyslog plugin by Alex Guensche ( http://www.zirona.com/software/donate ).
The firts version of this plugin was developed during a project with the German “Menschen für Tierrechte” (Humans for Animal Rights). 
It is an organisation of activists who advocate animal rights and fight against abuse of animals. They generously decided to donate 
this work to the general public by letting Zirona put it under the GNU GPL and allowing us to promote and distribute it.
Please support the work of Humans for Animal Rights, e.g. by placing a link to <a href="http://www.tierrechte.de/" title="www.tierrechte.de" rel="nofollow ugc">Humans for Animal Rights</a> and 
spreading the word. Not (only) because of this plugin, but generally for a better treatment of the beings on this planet.

wp2syslog

wp2syslog -- Global logging facility for WordPress (WPsyslog revisited)

Blobfolio

Jeepers Peepers provides an extensible interface for recording WordPress events — user logins, file uploads, post deletions, etc. — to a standard system log.
The resulting audit trail can then be incorporated into powerful log-monitoring tools like <a href="https://ossec.github.io/" rel="nofollow ugc">OSSEC</a> for pre-emptive protection and, in the unfortunate event of a hack, used as a vital reference in the post-mortem investigation.
The following events are automatically logged:
<ul>
<li>Content: <code>wp_die()</code> triggered;</li>
<li>Content: attachment deleted;</li>
<li>Content: attachment sideloaded;</li>
<li>Content: attachment uploaded;</li>
<li>Content: post deleted;</li>
<li>Content: post published; </li>
<li>Network: GET, HEAD, POST, etc., requests;</li>
<li>Plugin: activated;</li>
<li>Plugin: deactivated;</li>
<li>Plugin: upgraded;</li>
<li>User: deleted;</li>
<li>User: login banned (via <a href="https://wordpress.org/plugins/apocalypse-meow/" rel="ugc">Apocalypse Meow</a>);</li>
<li>User: login failed;</li>
<li>User: login succeeded;</li>
<li>User: new user;</li>
<li>User: password reset;</li>
</ul>
Each log entry records:
<ul>
<li>UTC timestamp;</li>
<li>Severity level;</li>
<li>User IP address (or <code>127.0.0.1</code> if automated);</li>
<li>Logged in username (if applicable);</li>
<li>Event message;</li>
</ul>
It will look something like this:
<pre><code>WordPressAudit 2017-05-24 16:35:45 [warning] yourdomain.com 68.256.55.123 "tiffany" "Deactivated plugin: look-see-security-scanner"
</code></pre>
<h3>Requirements</h3>
<ul>
<li>WordPress 4.7 or later.</li>
<li>PHP 7.3 or later.</li>
<li>Linux host.</li>
<li>Single-site instance.</li>
<li>Log file must be writeable by WordPress.</li>
</ul>
Please note: it is not safe to run WordPress atop a version of PHP that has reached its <a href="http://php.net/supported-versions.php" rel="nofollow ugc">End of Life</a>. Future releases of this plugin might, out of necessity, drop support for old, unmaintained versions of PHP. To ensure you continue to receive plugin updates, bug fixes, and new features, just make sure PHP is kept up-to-date. 🙂
<h3>Privacy Policy</h3>
Jeepers Peepers records CMS events such as post and plugin changes to a standard system log for security and audit purposes. Where possible, these entries include the public IP address and/or WordPress username of the individual responsible.
This plugin does not send any of this information to remote locations or third parties.
Please note: Jeepers Peepers DOES NOT integrate with any WordPress GDPR “Personal Data” features. (Selective erasure of audit logs would undermine the very purpose of this plugin! Haha.)

Jeepers Peepers: WP Syslog

An extensible tool for recording WordPress events to a system log.

wp2syslog vs Jeepers Peepers: WP Syslog