Audit
The Audit section gives you visibility into what your containers are doing at runtime. Container logs are streamed live from Docker and displayed in a built-in terminal viewer — no SSH session or command line required.
Container Logs
Every service running in an Application writes its output to Docker's log driver. The agent taps directly into that stream so you can read stdout and stderr without leaving the web interface.
Opening the Log Viewer
Click the Logs button (list icon) on any service row in the Applications page. A full-height drawer opens on the right side of the screen.
The drawer connects to the container immediately and starts streaming its output. The first batch is the last 200 lines of existing output; new lines arrive in real time as long as the drawer is open.
Reading the Output
| Element | Description |
|---|---|
| Timestamp (grey, left) | The time Docker recorded the line, shown as YYYY-MM-DD HH:MM:SS.mmm. |
| White text | Standard output (stdout) — normal container output. |
| Red text | Standard error (stderr) — warnings, errors, and crash messages. |
Output is rendered in a monospace font. Long lines wrap automatically. The viewer holds up to 1,000 lines in memory; older lines are discarded as new ones arrive.
Follow Mode
The Follow toggle at the top of the drawer controls whether new lines stream in automatically.
| Setting | Behaviour |
|---|---|
| Follow on (default) | A live SSE connection to the agent is kept open. New log lines appear as they are written. |
| Follow off | The connection closes after delivering the current tail. The output is a static snapshot. |
Turn Follow off when you want to read and scroll through a fixed output without new lines jumping in underneath you.
Auto-Scroll
When Auto-scroll is on (default), the viewer scrolls to the bottom automatically each time a new line arrives. Turn it off to hold your position while reading earlier output — new lines still accumulate at the bottom, but the view does not jump.
Clearing the Viewer
Click Clear to wipe all lines from the visible buffer. This does not affect the container's actual log history — clearing only removes what is displayed in the current session. Reopen the drawer to fetch a fresh tail.
Line Counter
The line count in the top-right corner of the toolbar shows how many lines are currently in the buffer. It resets to zero when you clear.
Viewing Logs for a Stopped Container
If a container has stopped, its historical log output is still available in Docker's log buffer. Open the log viewer for the service and turn Follow off — the viewer will fetch the tail of output that was written before the container exited.
This is useful for diagnosing a container that crashed on startup: read the last lines of stderr to find the error that caused it to exit.
Related Docs
- Applications — deploying and managing containers
- Alerts — anomaly alerts for sensor data