Disclaimer: You will need FTP access to your server to correctly use this plugin.
This plugin is for developers who want to monitor their debug.log file. Its purpose is to create a scheduled task
that splits the main debug.log file into interval based (e.g. daily, weekly) files.
Also it provides a simple way to send a customized log summary notification via email or Slack.
Do not activate it directly!! Follow Step 2 and Step 3 first.
In order to use this plugin you need to activate WordPress debug logging. Add the following to your wp-config.php file:
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );
@ini_set( 'display_errors', 0 );
It is important to customize the configuration before activating the plugin.
Navigate to wp-content/plugins/debug-log-monitoring directory using a FTP Client, duplicate the debug-log-monitoring.config.example.php file
and rename it to debug-log-monitoring.config.php. Adjust the configuration settings to your needs.
For a detailed explanation of all options, see section Config below.
Activate the plugin via the WordPress Plugin Management.
Note: The scheduler usually runs the first time directly after activation. And the next time after the configured interval. If you want to change the config and re-run the scheduler, please follow the steps below.
- Deactivate the plugin (this will reset and remove the scheduler)
- Adjust the config
- Activate the plugin
Following settings can be configured:
The name of your application or website. It is used to build the reporting summary message body.
Sets the time interval between two runs of the debug log monitoring. Valid values:
- "12_hours"
- "24_hours"
- "2_days"
- "1_week"
How many days the logs should be saved on disc before automatically removed.
The folder, in which the created logs will be stored - relative to wp-content/.
Truncate (clear) the main debug.log file after the interval log file has been created with the debug logs content.
Helps the plugin to validate, if the configuration needs to be updated, in case the plugin updates. Please check provided changelog in this case.
Enable sending a reporting summary via different channels. Before enabling, make sure at least one channel is properly configured.
An array of LogFilter sub arrays (associative) that define for which string occurences the report should be scanned. This is the base for creating the report. See example below.
The string sequence that should be counted within the log. A value of e.g. "PHP Fatal error:" will search the log for all occurences of php fatal errors.
The string that should be used in the notification message. E.g. "%d PHP Fatal Errors". The %d will be replaced with the actual count of the filterKey.
An array of Emoji sub arrays (associative) that define which emojis should be used in the notification message. See example below.
The threshold that defines, if the emoji should be used. E.g. if the threshold is 10 and the filterKey was found 5 times, the emoji will not be used.
The emoji string that should be appended in the slack notification message. E.g. ":fire:".
The emoji string that should be appended in the email notification message. E.g. "🔥".
Enable sending a reporting summary via slack.
The slack webhook url to send the notification to.
Enable sending a reporting summary via email.
An array of email addresses that should receive the notification.
The email address that should be used as sender. Please note: If you are using an SMPT Plugin like WP Mail SMTP, the sender address will be overwritten by the plugin.
The subject of the email notification.
The created log files are stored in the folder defined in the config option logsFolder. The default is wp-content/debug-logs.
Connect to your server via FTP and navigate to the folder. You should see the created log files.
The slack webhook url is a unique url that is used to send a message to a specific slack channel. Please follow the instructions on the slack website to create a webhook url: https://api.slack.com/messaging/webhooks
If you are using a local development environment, you might not receive any emails. This is because the plugin uses the WordPress function wp_mail().
We recommend to use a plugin like WP Mail SMTP to send emails locally. This way emails are also less likely to be marked as spam.
The schedular usually runs the first time directly after activation. Currently, there is no way to define a start time. As a workaround, you can deactivate the plugin, and activate it again at the specific time.
Currently, there is no UI to configure the plugin. All configuration is done via the config file.
You can easily add messages with the PHP build-in function
trigger_error(string $message, int $error_level = E_USER_NOTICE): bool
See here: https://www.php.net/manual/en/function.trigger-error.php
Please open an issue on GitHub: