Jeepers Peepers: WP Syslog


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 OSSEC 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:

  • Content: wp_die() triggered;
  • Content: attachment deleted;
  • Content: attachment sideloaded;
  • Content: attachment uploaded;
  • Content: post deleted;
  • Content: post published;
  • Network: GET, HEAD, POST, etc., requests;
  • Plugin: activated;
  • Plugin: deactivated;
  • Plugin: upgraded;
  • User: deleted;
  • User: login banned (via Apocalypse Meow);
  • User: login failed;
  • User: login succeeded;
  • User: new user;
  • User: password reset;

Each log entry records:

  • UTC timestamp;
  • Severity level;
  • User IP address (or if automated);
  • Logged in username (if applicable);
  • Event message;

It will look something like this:

WordPressAudit 2017-05-24 16:35:45 [warning] "tiffany" "Deactivated plugin: look-see-security-scanner"


  • WordPress 4.7 or later.
  • PHP 7.3 or later.
  • Linux host.
  • Single-site instance.
  • Log file must be writeable by WordPress.

Please note: it is not safe to run WordPress atop a version of PHP that has reached its End of Life. 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. πŸ™‚

Privacy Policy

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.)

Lluniau Sgrin

  • Example log file.


Nothing fancy! You can use the built-in installer on the Plugins page or extract and upload the jeepers-peepers folder to your plugins directory via FTP.

To install this plugin as Must-Use, download, extract, and upload the jeepers-peepers folder to your mu-plugins directory via FTP. Please note: MU Plugins are removed from the usual update-checking process, so you will need to handle future updates manually.

Cwestiynau Cyffredin

Is this compatible with Multi-Site?

Sorry, no. This plugin can only be added to standard (single-site) WordPress installations.

The log isn’t updating…

  1. Make sure the log file exists. The default location is /var/log/wordpress/{YOUR_SITE_DOMAIN}.log, but this can be overridden by defining a constant in your wp-config.php file (see the relevant FAQ section below).
  2. Make sure WordPress/PHP can reach the file. For PHP sites with open_basedir restrictions, this means whitelisting the path to the log file. If the hosting environment is chrooted or jailed, the log location will need to be within the same boundaries.
  3. Make sure the log file’s ownership/permissions allow PHP to write changes to it. This varies by environment, but a good place to start is assigning the same owner:group to the log file used by your WordPress files.

Does this require any theme or config changes?

By default, the log is written to /var/log/wordpress/{YOUR_SITE_DOMAIN}.log. If this path exists and works for you, then no, logging will happen without any intervention.

To modify the default behavior, you will need to define a couple constants in your wp-config.php file. See the relevant FAQ section below.

List of configuration constants

The following constants can be defined in your wp-config.php file to override the default behaviors.

  • (string) BLOBAUDIT_SITE_URL Your site’s domain, for logging purposes. By default, this will be your site’s domain name, lowercased, and without a leading www. subdomain.
  • (string) BLOBAUDIT_LOG_PATH The absolute path to the log file. Default: /var/log/wordpress/{YOUR_SITE_DOMAIN}.log

When using a custom log location, please choose one that is outside the web root. You don’t want just anybody looking at it. πŸ™‚

Logging custom events

The plugin includes action callbacks you can trigger in your code to record a custom event.

// In order of severity...
do_action('syslog_debug', $message, $internal);
do_action('syslog_notice', $message, $internal);
do_action('syslog_info', $message, $internal);
do_action('syslog_warning', $message, $internal);
do_action('syslog_error', $message, $internal);
do_action('syslog_critical', $message, $internal);

All actions accept the following:

  • (string) $message The event message.
  • (bool) (optional) $internal Prefix the severity with an @ to mark it as “internal”. Default: FALSE


Mehefin 14, 2018 2 replies
Would be neat to have some recommended additional OSSEC rules if possible – right now I’m not doing anything special but I suppose some additional rules may be useful. Thanks for submitting this though!
Read all 1 review

Contributors & Developers

“Jeepers Peepers: WP Syslog” is open source software. The following people have contributed to this plugin.


Cofnod Newid


  • [New] Log network requests.
  • [Improve] Minor code optimizations.


  • [New] Add privacy policy hook for GDPR compliance.


  • [New] Initial launch!