Skip to content
Avaloi

View logs

Read the error, PHP, access, slow, and cache logs live in the dashboard, search and filter them, download them, and clear them on staging.

The Log viewer shows the newest lines of each log for an environment and keeps adding new lines as they arrive. Open the site, pick the environment in the top bar, then choose Logs.

The logs

Tab What it holds
error.log Nginx errors: missing files, upstream timeouts, refused requests.
php-error.log PHP warnings, notices, and fatal errors, and PHP-FPM pool messages.
access.log One line per request.
slow.log PHP requests that ran longer than 5 seconds, with the function they were stuck in.
cache-perf.log The page cache result for each request: HIT, MISS, BYPASS, or EXPIRED.
  • Lines picks how many recent lines to load: 100, 500, or 1,000.
  • Live adds new lines as they arrive. Turn it off to read without the view moving; new lines wait until you turn it back on.
  • Search highlights matches in the loaded lines.
  • Filter by Error, Warning, Notice, or Info to show one level.
  • The reload button loads the lines again. The download button saves the last 1,000 lines as a file.

Clear a log on staging

On a staging environment, the clear button empties the log. Download it first if you need the lines. It runs as a job, so it shows in the job list and the activity log.

Logs on live can not be cleared, so they stay for support.

Accessibility

Screen readers hear new error lines in short batches, not one by one, so a busy log does not flood the reader.

Quick answers

Which log do I start with? php-error.log, filtered to Error, for a broken page. error.log for 404s and timeouts.

Why does the cache log show BYPASS for a page? A page is not cached for a logged in visitor, a cart, a POST, or a static file. See Edge cache and CDN.

API

  • GET /v1/environments/{id}/logs/{file}
  • GET /v1/environments/{id}/logs/{file}/stream
  • GET /v1/environments/{id}/logs/{file}/download
  • POST /v1/environments/{id}/logs/{file}/clear with {"confirm": true} (staging only; live answers 409)

In the API, {file} is error, php-fpm, access, slow, or cache. The stream endpoint sends server-sent events, one LogStreamEvent per data field.

Still stuck?

Email [email protected] with your site name and what you tried, or send us a message.