Skip to content

Monitoring and Logs Updated 2026-05-27

Viewing log files

The dashboard log viewer — per-node log file access with tail-style auto-refresh, the log files available for each stack, and how to grab logs over FTP.

Log files are the first place to look when something is off. The platform exposes every container’s standard log files through the dashboard with a tail-style viewer, so you do not need SSH access to read what an application is saying.

Opening logs

  1. Sign in to the dashboard.
  2. Click the Log icon next to the node you want to inspect.
  3. The log tab opens at the bottom of the dashboard. If the layer has multiple nodes of the same type, pick the specific node from the dropdown.

Above the log text:

  • Clear — empty the displayed log buffer (the file on disk is untouched).
  • Refresh — re-read the log file now.
  • Prev / Next — navigate through the log body for large files.

Auto-refresh

The viewer auto-refreshes every 3 seconds by default. That makes it usable as a live tail during deployments, installations, or active troubleshooting — you do not have to manually pull the latest lines.

When you want to focus on what is on screen — analyzing a stack trace, for example — uncheck Auto refresh in the dropdown above the log output. Re-enable it the same way when you are done.

Deleting log files

Old log files can be deleted directly from the list. Hover over the file you want to remove and click the cross icon, or select it and press Delete in the toolbar. The file is removed from the container’s disk.

This is useful for cleaning up rotated logs you no longer need, especially when disk usage is getting close to the limit. Be conservative — once deleted, the file is gone.

Logs over FTP

Logs can also be downloaded through FTP. The FTP add-on exposes the logs directory of the container, so you can pull files into a local editor or feed them to a downstream tool. See the FTP/FTPS support page for installation and credentials.

Available log files by stack

What is in the log list depends on the stack. The standard files are:

  • Tomcat 6/7, TomEE — manager, localhost_access_log, catalina, host-manager, localhost
  • Jetty — {date} (per-day file), request
  • GlassFish — {date} (per-day file), request
  • MySQL / MariaDB — mysqld
  • PostgreSQL — postgresql-{day of week}
  • CouchDB — couch
  • Apache — access-log, dummy-host, error_log
  • NGINX PHP — error, access, php-fpm
  • NGINX load balancer — tcp_access, error, error_log, access, localhost
  • Memcached — memcached
  • Node.js — node

Other stacks (custom Docker, Kubernetes) expose their own log files through the same viewer; the file list depends on what the container writes.

Git/SVN deploy logs

If you deploy from a remote Git or SVN repository, a vcs_update log file appears on the build node — Maven for Java projects, Apache or NGINX for PHP. The file contains the build and deploy output for each pull. When a deployment fails, this is the file to read.

Where to go from here

  • Statistics monitoring — the metrics side of the same diagnostic flow.
  • Load alerts — for getting notified before you need to dig into logs.
  • FTP/FTPS support — adding FTP access to pull logs in bulk.