Title: Jeepers Peepers: WP Syslog
Author: Blobfolio
Published: <strong>2017年5月26日</strong>
Last modified: 2026年9月30日

---

プラグインを検索

![](https://ps.w.org/jeepers-peepers/assets/banner-772-250.png?rev=2889645)

![](https://ps.w.org/jeepers-peepers/assets/icon-256x256.png?rev=2889645)

# Jeepers Peepers: WP Syslog

 作者: [Blobfolio](https://profiles.wordpress.org/blobfolio/)

[ダウンロード](https://downloads.wordpress.org/plugin/jeepers-peepers.0.5.5-b.zip)

 * [詳細](https://ja.wordpress.org/plugins/jeepers-peepers/#description)
 * [レビュー](https://ja.wordpress.org/plugins/jeepers-peepers/#reviews)
 *  [インストール](https://ja.wordpress.org/plugins/jeepers-peepers/#installation)
 * [開発](https://ja.wordpress.org/plugins/jeepers-peepers/#developers)

 [サポート](https://wordpress.org/support/plugin/jeepers-peepers/)

## 説明

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](https://ossec.github.io/) 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](https://wordpress.org/plugins/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 `127.0.0.1` if automated);
 * Logged in username (if applicable);
 * Event message;

It will look something like this:

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

### Requirements

 * WordPress 4.7 or later.
 * PHP 7.4 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](http://php.net/supported-versions.php). 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.)

## スクリーンショット

[⌊Example log file.⌉⌊Example log file.⌉[

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](https://codex.wordpress.org/Must_Use_Plugins),
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.

## FAQ

### 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`
 * (_bool_) **BLOBAUDIT_LOG_UTC** Record datetimes in UTC rather than the site’s
   timezone. Default: `true`

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`

## 評価

![](https://secure.gravatar.com/avatar/66ff6914a0b3130e9f93ab6052083af2277b9888894b3f22e01579fc07251b9c?
s=60&d=retro&r=g)

### 󠀁[Does what it is supposed to do](https://wordpress.org/support/topic/does-what-it-is-supposed-to-do-37/)󠁿

 [d1nwp](https://profiles.wordpress.org/d1nwp/) 2024年9月22日

easy installation and configuration fast response by the author

![](https://secure.gravatar.com/avatar/341878b8cfabcdf17c909340c11049e6178e52531861e6cfa13f0b1b1b721297?
s=60&d=retro&r=g)

### 󠀁[Looks great so far](https://wordpress.org/support/topic/looks-great-so-far-3/)󠁿

 [robkumd](https://profiles.wordpress.org/robkumd/) 2018年6月14日 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!

 [ 1件のレビューをすべて表示 ](https://wordpress.org/support/plugin/jeepers-peepers/reviews/)

## 貢献者と開発者

Jeepers Peepers: WP Syslog はオープンソースソフトウェアです。以下の人々がこのプラグ
インに貢献しています。

貢献者

 *   [ Blobfolio ](https://profiles.wordpress.org/blobfolio/)

[“Jeepers Peepers: WP Syslog” をあなたの言語に翻訳しましょう。](https://translate.wordpress.org/projects/wp-plugins/jeepers-peepers)

### 開発に興味がありますか ?

[コードを閲覧](https://plugins.trac.wordpress.org/browser/jeepers-peepers/)するか、
[SVN リポジトリ](https://plugins.svn.wordpress.org/jeepers-peepers/)をチェックする
か、[開発ログ](https://plugins.trac.wordpress.org/log/jeepers-peepers/)を [RSS](https://plugins.trac.wordpress.org/log/jeepers-peepers/?limit=100&mode=stop_on_copy&format=rss)
で購読してみてください。

## 変更履歴

#### 0.5.5

 * [Docs] Bump “Tested up to” version to 7.1.
 * [Docs] Bump “Requires PHP” version to 7.4.
 * [Lint] Remove old PHP workaround.

#### 0.5.4

 * [New] `BLOBAUDIT_LOG_UTC` constant for toggling between UTC/site-time for event
   dates.

#### 0.5.3

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

#### 0.5.2

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

#### 0.5.1

 * [New] Initial launch!

## メタ

 *  バージョン **0.5.5**
 *  最終更新日 **2週間前**
 *  有効インストール数 **70+**
 *  WordPress バージョン ** 4.7またはそれ以降 **
 *  検証済み最新バージョン: **7.2**
 *  PHP バージョン ** 7.4またはそれ以降 **
 *  言語
 * [English (US)](https://wordpress.org/plugins/jeepers-peepers/)
 * タグ
 * [audit trail](https://ja.wordpress.org/plugins/tags/audit-trail/)[event log](https://ja.wordpress.org/plugins/tags/event-log/)
   [security](https://ja.wordpress.org/plugins/tags/security/)[syslog](https://ja.wordpress.org/plugins/tags/syslog/)
   [system log](https://ja.wordpress.org/plugins/tags/system-log/)
 *  [詳細を表示](https://ja.wordpress.org/plugins/jeepers-peepers/advanced/)

## 評価

 5つ星中5つ星

 *  [  2 5-星レビュー     ](https://wordpress.org/support/plugin/jeepers-peepers/reviews/?filter=5)
 *  [  0 4-星レビュー     ](https://wordpress.org/support/plugin/jeepers-peepers/reviews/?filter=4)
 *  [  0 3-星レビュー     ](https://wordpress.org/support/plugin/jeepers-peepers/reviews/?filter=3)
 *  [  0 2-星レビュー     ](https://wordpress.org/support/plugin/jeepers-peepers/reviews/?filter=2)
 *  [  0 1-星レビュー     ](https://wordpress.org/support/plugin/jeepers-peepers/reviews/?filter=1)

[Your review](https://wordpress.org/support/plugin/jeepers-peepers/reviews/#new-post)

[すべてのレビューを見る](https://wordpress.org/support/plugin/jeepers-peepers/reviews/)

## 貢献者

 *   [ Blobfolio ](https://profiles.wordpress.org/blobfolio/)

## サポート

意見や質問がありますか ?

 [サポートフォーラムを表示](https://wordpress.org/support/plugin/jeepers-peepers/)

## 寄付

このプラグインが今後も改善できるよう応援しませんか ?

 [ このプラグインに寄付 ](https://blobfolio.com/donate.html)