View, Filter and Search Your WordPress Logs

Dealing with logs is often painful, requires command-line skills and regex-fu. This is why we’ve been working on a new UI here at Pressjitsu, which helps you view, filter and search your WordPress server logs, all from a simple web interface.

The New Logs UI

Pressjitsu Logs UI
Pressjitsu Logs UI

You can access the new interface from your Pressjitsu control panel. Each log entry is presented in a table row, which can be expanded to show additional details, including the response code, hostname, request method and URI, origin IP address, referer, time taken to complete the request, cache status and more.

Pressjitsu Log Filters
Pressjitsu Log Filters

You can use the filters panel to narrow down your request. A good example would be a search on all log entries with a 404 status code to find requests hitting your “not found” page. You can then use a WordPress plugin to point these in the right direction.

For users running WordPress Multisite, the Hosts filter is a particularly useful one to track down problems with a specific site in your network.

Some of the filters also accept wildcard searches, for example if you’d like to see all requests hitting any of your WordPress JSON API endpoints, you can filter the request URI using a wildcard: /wp-json/*.

Accessing Logs via SSH

If you’re a geek and you’d rather browse logs via the command line. Links to the nginx access and error log files are available in your home directory under logs:

tail -f ~/logs/access.log
tail -f ~/logs/error.log
Pressjitsu Logs via SSH
Pressjitsu Logs via SSH

The raw logs you’ll see on your server come in the native nginx format and can be used with various open source filtering, searching and analysis tools. However this places a limit on what data is available in those logs, for example you won’t see the cache status or the upstream response time, so we recommend you try our web-based UI instead.

Old Logs

We rotate logs at least once every day on all Pressjitsu servers, sometimes more often for high-traffic sites, but we tend to keep archived log files for as long as 52 weeks, which means they can be accessed with tools such as zcat from the command line.

The web-based interface, however, indexes only the most recent 7 days of data using Logstash and Elasticsearch, though if you need access to older data, we’ll be happy to help you out.

As always, if you have any feedback or requests about this new feature, please leave us a note via e-mail or by opening a new support request via your hosting control panel.