Logs
vastframe keeps two kinds of logs per deployment, plus a log per scheduled job run.
| Log | What's in it |
|---|---|
| Build | Detection result, the build output, migrations applied, health check |
| Runtime | Your app's stdout and stderr |
| Job runs | Each cron or worker run's output, with a header naming the run, trigger and command, and the exit status |
In the console
Open the project's Logs page. Pick a deployment (the latest by default) and switch between build and runtime output. Filter lines narrows the view, and the view follows new lines while you're scrolled to the bottom. While a deployment is in progress the build log updates live. Scheduled jobs at the bottom of the page shows job runs.
From the CLI
tc logs # build and runtime of the latest deployment (last 200 lines)
tc logs --build # build only
tc logs --runtime --tail 1000 # runtime, last 1000 lines
tc logs --deployment d7f3a2 # a specific deployment
--tail accepts 1 to 5000 lines.
From MCP
get_logs returns build and runtime output, so an agent can read a failed build and fix it.
From the API
GET /api/projects/q3-variance/logs?type=build|runtime|all&tail=200&deployment=d7f3a2
Tips
- Log to stdout and stderr; don't write log files inside the container, which is replaced on every deploy.
- A failed deploy leaves production on the previous deployment; the build log of the failed deployment says why.
- Errors from the SDK carry a
codeand afix. Log both.
Availability
On the local stack logs come from the container runtime. On Azure they come from Log Analytics; that driver is coming soon.
Was this page helpful?