Logs — build & application

PandaStack streams two distinct kinds of logs, and it helps to know which one you’re looking at:

Log type	What it shows	When it runs	Available for
Build logs	The output of building your project — dependency install, framework compile, image build. Where a failed build’s error appears.	While a deployment builds (queued → running).	Static and container projects
Application logs	The live stdout/stderr of your running app — the server booting, requests, your own console.log/print output.	Continuously, from the moment the app is live.	Container projects only

Static sites serve pre-built files from the CDN and run no application server, so they have build logs only — there is no runtime process to stream. Container apps have both.

Build logs

Build logs stream live while the build runs — you see output as it happens, not only after the build finishes. If a deployment fails, this is where the error is. They’re shown by default on a deployment while it builds.

GET /v1/deployments/:uuid/logs/stream

Streamed over Server-Sent Events, keyed by the deployment UUID. See Build & buildpacks for what runs during a build.

Application (runtime) logs

Once a container app is live, its application logs stream the running pod’s stdout/stderr — the same output you’d see with kubectl logs or docker logs, tailed to your dashboard in real time. Use these to watch your server boot after a deploy, confirm it’s serving, and debug runtime errors (a crash loop, an unhandled exception, a bad env var).

GET /v1/projects/:name/app-logs/stream

Streamed over Server-Sent Events. The API proxies the live pod log stream from the worker and re-frames each line for the browser.

Note

Application logs are container-only. Requesting them for a static project returns a done event with reason not-container — static sites have no runtime process, only build logs.

From the dashboard

Open the project, then the Logs tab. A container app shows its live application logs there; a static project shows build logs from its latest deployment.

From the CLI

panda projects logs streams the latest deployment’s logs. Pass --type to choose which stream:

# Build logs (the default)
panda projects logs my-app

# Live application logs (container apps)
panda projects logs my-app --type application

Flag	Values	Default
--type	build or application	build

See the CLI command reference for the full command list.

Which log do I want?

• My build failed. → Build logs. The compiler/installer error is there.
• My build succeeded but the site/app is broken. → For a container app, application logs — the app started but is erroring or crash-looping. For a static site, check the browser console and redirects/rewrites; there’s no server to log.
• I want to watch my app boot after a deploy. → Application logs (container).

Related

• Build & buildpacks — what runs during a build
• Container apps — the runtime your application logs come from
• Rollbacks — undo a bad deploy
• Build & deploy failures — common build errors