Log viewer

Gigabytes open instantly

Only the last 256 KB of a file is read, never the whole thing. A MySQL error log that has grown past three gigabytes, which happens, quietly, over a couple of years, opens as fast as an empty one.

  • System logs first, then one entry per virtual host
  • Filter by text to keep only the lines that matter
  • Follows the file as it grows, if you were already at the bottom
  • Opens with ⌘L from anywhere in the app
error_log
Apache, error_log error Refresh [Fri Aug 07 09:14:22] [core:error] [pid 2282] File does not exist: /www/projects/example1/favicon.ico [Fri Aug 07 09:18:04] [php:error] [pid 2284] Uncaught Error: Call to undefined function in /www/projects/example1/src/Cart.php:88 [Fri Aug 07 09:22:41] [mpm_prefork:notice] Apache configured -- resuming normal operations error_log · 840 KB · showing the end of the file

When a log will not open

MySQL's error log belongs to the _mysql user, and your account cannot read it. Rather than showing an empty window, the viewer says so and offers a one-off read with administrator rights. Automatic refresh switches off at that point, so you are not asked for a password every two seconds.

Per-project logs

Each virtual host writes its own error and access log, and they appear in the selector under the system ones. When a single site misbehaves you can go straight to it instead of reading everything at once.

⚠️ Logs grow silently

Nothing rotates them by default. On the machine this app was built on, the MySQL error log had reached 3.6 GB without anyone noticing. The viewer opens it regardless, but a file that size usually means an error repeating thousands of times a day, and it is worth reading.

Stop guessing what broke

Open the log, filter for the error, read the line.

v9.26.17Updated November 2026Free · app and dashboard GPL