Skip to main content
An OpenHands Enterprise VM installation writes the output of every service to log files on the VM. To bring those logs into your observability platform, install your platform’s log agent on the VM and point it at those files. For one-off diagnostics, collect a support bundle instead. See Troubleshooting.

​
Where the Logs Are

Application logs live under /var/log/pods. Each path is built from the namespace, the pod, and the container:
For example:
The VM installation writes to files ending in .log. It rotates a file once it grows large, appending a timestamp to the name and compressing it, for example 16.log.20260824-235907.gz. A pattern ending in *.log therefore collects current output and skips the rotated copies. /var/log/containers holds a symlink to every one of those files, carrying the same details in the file name rather than in the directories:
Log agents with built-in Kubernetes support read that directory, because they can take the pod and container names straight from the file name. The application log files are readable only by root.
The VM keeps only recent output, roughly 50 MB per service, and the log files for a sandbox are deleted when its conversation is cleaned up. Run your log agent continuously and set your retention period in your observability platform.

​
Collect the Logs

1

Install your log agent

Install the Linux log agent for your observability platform on the VM, following your vendor’s instructions. Run it as root so that it can read the log files.
2

Tail the application logs

Configure a file input for /var/log/pods/*/*/*.log, or /var/log/containers/*.log if your log agent reads the symlinks.Every line begins with a timestamp and the output stream:
Enable your log agent’s parser for this format, called cri in Fluent Bit, so that the timestamp and the message arrive as separate fields. The message itself is JSON.
3

Collect the journal

Enable your log agent’s journald input to pick up cluster and operating system logs.
4

Confirm the logs arrive

Print a recent line on the VM, then search for it in your observability platform:
5

Repeat on every VM

A VM only holds the logs for the services that run on it. Repeat these steps on each VM in the installation, including any VM that runs sandboxes.

Troubleshooting

Collect a support bundle and inspect workloads.

Admin Console Configuration

Configure a Replicated VM installation.