LogWatch

FAQ

Where does LogWatch read logs from?

LogWatch automatically detects available PHP error logs on your server, including:
* PHP ini error_log setting
* WordPress debug.log
* Apache/Nginx error logs
* Custom log files in your document root

You can also enable the Custom Error Handler to create a dedicated log file.

What if I’m on shared hosting and can’t access system logs?

Enable the Custom Error Handler in Settings. This creates a protected log file at wp-content/uploads/logwatch/php-errors.log that captures all PHP errors without requiring server access. Perfect for shared hosting environments like Bluehost, SiteGround, or GoDaddy.

Can I export the logs?

Yes! Click the Export CSV button on the Logs page to download all visible errors in CSV format for external analysis, sharing with your team, or importing into other tools.

How does error grouping work?

LogWatch groups identical errors (same file, line, and message) together and shows you:
* Total occurrence count
* First seen timestamp
* Last seen timestamp
* Full stack trace

This helps you focus on unique issues instead of seeing the same error repeated thousands of times. For example, if a deprecated function is called 5,000 times, you’ll see one grouped entry showing “5,000 occurrences” instead of 5,000 separate entries.

Can I hide errors I’ve already fixed?

Yes! Click Mark as Fixed next to any error to hide it from the main view. You can view and restore hidden errors from LogWatch → Hidden Logs anytime. This keeps your logs clean and focused on active issues.

Does LogWatch slow down my site?

No. LogWatch only reads log files when you view the admin pages – it has zero impact on your frontend performance. The dashboard widget loads asynchronously so it won’t slow down your dashboard. Log parsing is optimized for large files using reverse reading techniques.

What log formats are supported?

• PHP error_log format (standard PHP errors)
• Apache error log format
• Nginx error log format
• WordPress debug.log format
• Custom log formats with PHP error messages

Is LogWatch compatible with PHP 8?

Yes! LogWatch is fully compatible with PHP 7.4, 8.0, 8.1, 8.2, and 8.3. We test on all major PHP versions to ensure compatibility.

Will LogWatch work with my hosting provider?

Yes! LogWatch works on any hosting provider:
* Shared Hosting – Use Custom Error Handler (Bluehost, SiteGround, HostGator, GoDaddy, etc.)
* VPS/Cloud – Auto-detects system logs (DigitalOcean, Linode, Vultr, AWS, etc.)
* Managed WordPress – Works with WP Engine, Kinsta, Flywheel, Pressable
* Local Development – Perfect for XAMPP, MAMP, Local by Flywheel, Docker

Can I monitor multiple sites?

Yes! Install LogWatch on each site you want to monitor. Each installation monitors its own logs independently. For centralized multi-site monitoring, check out LogWatch Pro.

Does LogWatch capture all PHP errors?

LogWatch displays errors that are logged by PHP. Make sure error logging is enabled in your php.ini or wp-config.php:

define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);

Alternatively, enable the Custom Error Handler in LogWatch settings to automatically capture all errors.

What’s the difference between LogWatch and LogWatch Pro?

LogWatch (Free):
* View and parse error logs
* Smart error grouping
* Filter by error type
* CSV export
* Dashboard widget
* Hide/unhide errors

LogWatch Pro:
* Everything in Free, plus:
* Real-time Slack/Discord notifications
* Email alerts for critical errors
* Advanced error analytics and trends
* Performance monitoring
* Scheduled reports
* Priority support

Compare features →

How do I enable WordPress debug mode?

Add these lines to your wp-config.php file (above the “That’s all, stop editing!” line):

define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);

This enables error logging to wp-content/debug.log without displaying errors on your site.

Can I use LogWatch on a production site?

Yes! LogWatch is safe for production use. It only reads log files and doesn’t modify your site’s code or database (except for storing hidden error preferences). The admin interface is only accessible to users with “manage_options” capability (administrators).

Does LogWatch work with multisite?

Yes, LogWatch works on WordPress multisite installations. Each site in the network can have its own LogWatch configuration.

I don’t see any errors. What’s wrong?

If you don’t see any errors, it could mean:
1. No errors are occurring – Great! Your site is error-free
2. Error logging is disabled – Enable WP_DEBUG_LOG in wp-config.php
3. Wrong log file selected – Try enabling Custom Error Handler in Settings
4. Log file permissions – Ensure the web server can read the log file

Check the Settings page to see which log file is being monitored and when it was last modified.

Can I filter errors by date?

Currently, LogWatch shows all errors in the selected log file, sorted by most recent. Date-range filtering is planned for a future update. You can export to CSV and filter by date in Excel/Google Sheets.

How often should I check LogWatch?

We recommend:
* Development sites – Check after each major change
* Staging sites – Check before deploying to production
* Production sites – Check weekly, or enable LogWatch Pro for real-time alerts

The dashboard widget gives you a quick glance every time you log in.

Is LogWatch GDPR compliant?

Yes. LogWatch reads log files locally on your server and doesn’t send any data to external services (unless you enable Pro features like notifications). Error logs may contain IP addresses depending on your server configuration, so treat them according to your privacy policy.