Logs & events
Stream build and runtime logs live, and read back the deploy timeline and activity feed.
VAC streams everything that happens to your app — build output, container logs, deploy progress — into the dashboard in real time over WebSocket, and keeps enough history to answer "what changed?"
Build vs. runtime logs
| Build logs | Runtime logs | |
|---|---|---|
| Source | docker compose build / up output during a deploy | container stdout/stderr while running |
| Tagged by | service + stream (stdout/stderr/system) | service + stream |
| Retention | kept with the deployment record, indefinitely | ~7 days, capped at ~10,000 lines per service |
| Where | Deployments tab → expand a deployment | Logs tab |
Both stream live as they're produced; the dashboard de-duplicates the replayed backlog against the live tail so you never see a line twice.
Live streaming
The dashboard subscribes to per-resource topics over a single WebSocket:
- build logs for the deployment you're watching,
- runtime logs for an app (tagged per service, filterable),
- stats for an app (per-service CPU/RAM — only collected while someone is watching),
- host vitals (CPU/RAM/disk and aggregate request rate),
- deploy queue changes across all apps.
A connection badge shows live/reconnecting state, and you can filter runtime logs by service and export them.
Deploy timeline
The Deployments tab is the audit trail for what's gone live. Each deployment records:
- status —
queued→cloning→building→deploying→health-checking→running(orerror/interrupted/canceled), - commit SHA and message,
- trigger —
manual,push,tag,rollback, orsystem, - timestamps and duration.
Expand a row to replay its build logs and per-phase progress, or to roll back to that version if it was a successful deploy. VAC keeps the most recent 20 deployments per app; older ones are pruned automatically.
Activity feed
Beyond deploys, VAC keeps an activity / audit log of operator actions — who did what, from which session or API token, with the result. Entries record the actor (user, API token, system, or anonymous), the action and target, and metadata. A curated set of safe actions (like domain or env changes) are revertable straight from the feed, with a before/after diff (secrets masked). Activity is retained for 30 days.