:::meta author=Docs-Team updated=2026-09-03 tags=logs,streaming,history,download
:::
:::breadcrumb Docs > User Guide > Logs
:::
:::reading-time
:::
The Logs tab gives you two synchronized panels: Service logs streamed live from the running container, and Deploy history — the build events of a chosen deploy. Both use the same log viewer with live connection chips, level filtering, two search modes, and download/copy/clear actions. Logs are retained on the server for a limited window, so you can search history that is no longer loaded in your browser.
:::toc
:::
The log viewer
Both panels share one interface, so learning it once covers both. The header row carries:
• A connection chip: Live (green) while the WebSocket stream is open, Offline (grey, clickable to retry) when it drops, and Reconnecting… while it tries to recover.
• A count chip: {n} loaded, or {n} shown of {m} loaded when filters reduce the view.
• A Paused chip appears when you freeze the stream.
The toolbar buttons: Refresh, Pause / Resume (pausing freezes both the stream and auto-scroll), and Jump to latest — a floating button on mobile — which scrolls you back to the tail. The More actions menu (⋮) contains the bulk tools:
| Menu item | What it does |
| --- | --- |
| Download from server | Exports the retained server history |
| Download view | Downloads exactly the lines currently shown |
| Copy view | Copies the shown lines to the clipboard |
| Clear view | Clears loaded lines in this view only — server logs are not deleted, with a confirmation dialog to say so |
Filtering and searching
Each log line renders with its timestamp, a level chip (ERROR, WARNING, INFO, DEBUG), a deploy stage chip during builds, a progress percentage when the stage reports one, and the monospace message. Long lines collapse with Show more / Show less.
The Level selector filters to a single level — All, Info, Warning, Error, or Debug. Search has two modes, toggled with Local / Server history:
:::compare Local filter | Server search
=== Local filter
• Instant, works offline
• Only filters lines already loaded in the view
• Best for scanning what you just watched
=== Server search
• Queries the backend's retained history
• Finds events that scrolled away or predate your session
• Results load into the view with a loading indicator
:::
At the top of the service-log panel, Load older logs (and automatic load-on-scroll-up) pages back into history. A retention line under the header summarizes the server window: Retention Nd · Storage NMB / MMB · dropped K. When the stream detects a gap, a dismissible warning points it out so you know to search the server history instead.
Service logs
The Service logs panel — subtitle "Live stream + retained history" — is the container's stdout/stderr. While your service runs, lines arrive over the WebSocket and the view auto-scrolls; pausing stops both. The empty state, "No service logs yet.", means the container has not produced output (or has never started).
:::tip
Pair the logs with the control bar's Check status button when a service misbehaves: the probe refreshes the CPU/RAM meters, and the next log lines usually explain what the runtime is doing.
:::