Presslabs logging system

For every development process you need logs to check that the work you're performing is actually doing what it's supposed to do. Besides that, logs help you identify and fix issues that might appear on your site.

Where can I access the site logs?

The logs we provide for your site are accessible in the Presslabs dashboard, on the Sites section, Logs menu.

You'll notice the Log settings tab, and there's where you can control the verbosity of log messages.

  • Log level - this sets the level for the logs are generated for your site:
  • ERROR - only fatal errors are logged. This means all PHP fatal errors and E_USER_ERROR.
  • WARNING (Default setting)d - warnings are logged as well. This extends ERROR level with E_WARNING, E_CORE_WARNING, E_COMPILE_WARNING, E_USER_WARNING.
  • INFO - this logs everything, including E_USER_NOTICE, E_NOTICE, E_DEPRECATED, E_USER_DEPRECATED, E_STRICT.
  • DEBUG - besides all the above, this also sets the WP_DEBUG constant to true and changes the way errors are displayed by including the stack trace.

!!! note That displaying the stack trace can expose sensitive information, so use it carefully on production websites.

What kind of information can I find in the logs?

This obviously depends on the log level you've set for the site. Besides the standard php and WordPress related logs, we're adding various other logs, such as:

  • Cache refresh notifications - these indicate URL's that take a long time to refresh, or errors related to cache refreshes.
  • database errors - errors or notifications from MySQL
  • transactional e-mails - details about e-mails sent from WordPress (such as comment notifications, new users, contact forms etc.)
  • php-fpm notifications - these contain errors or notifications from php-fpm