Jeepers Peepers: WP Syslog

Hỏi đáp

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