Logs

The project's Logs page separates three sources that are commonly conflated. They have different authors, and calling all three "logs" sends someone hunting for an application error in a place that only holds the deployment's narrative.

Tab	Who wrote it	When to look here
Runtime	Your application, on stdout and stderr	The application started and something is wrong with its behavior
Build	The image builder	The deployment failed before starting up
Platform	Zero, while deploying	To understand what the platform did, and in what order

"The platform said the version is live" and "the application said it could not connect to the database" are sentences from different authors.

Runtime

The standard output and error output of your application's processes.

• Choose the period and, if there is more than one service, the service.
• Use the search field to filter by text.
• Copy an excerpt with the copy button.

If no application is running yet, the answer is explicit: there is no run yet. Never an empty list — empty would mean "it ran and wrote nothing", and confusing the two sends you looking in the wrong place.

For the application to appear here, it has to write to stdout/stderr. Applications writing to a file inside the container are not collected.

Build

The image builder's full output, chosen per deployment.

The output is recorded in both outcomes — success and failure. Someone investigating a slow build, or one that produced the wrong image, needs the log of a build that succeeded.

This is the tab that answers "why did it break" when a deployment fails at Building. See How the image is built.

Platform

What Zero recorded while deploying: the steps, the transitions, and the reasons. It is the operation's narrative, in product language.

The same content appears under the Events tab of a deployment's page, restricted there to that deployment.

Secrets

Credentials appearing in the output are masked before being stored — including those arriving in external tools' messages. The surrounding context is preserved: a fully masked line solves the leak and creates a useless log.

Common errors

Symptom	Likely cause	What to do
The Runtime tab shows nothing	There is no run yet, or the application does not write to stdout	Check the deployment state and how your application logs
The build log is empty	The deployment failed before the build	Check Deployment attempts in the project
I cannot find the error I saw in the browser	The error is the application's, not the platform's	The Runtime tab, not Platform

Next steps

• Traffic and consumption
• Following a deployment
• Common problems