Read an app's logs
Logs streams the log of the pod your app runs in. It is the first place to look when an app is up but behaving oddly, and the second place when a deploy fails.
Who can use it: the Builder role or higher.
The stream
The tab fetches a snapshot first so there is something to read immediately, then connects a live stream on top of it. Lines arrive as the app writes them.
The controls are Pause, Refresh, Download and Jump to bottom. Pausing holds the view still while the stream keeps running underneath, so nothing is lost while you read.
The tail counter
Underneath the stream, a counter says how many lines you have and what the connection is doing. It is the quickest way to tell a quiet app from a broken pipe.
| It reads | What it means |
|---|---|
| streaming live | Connected. Lines appear as the app writes them |
| paused | You pressed Pause. The stream is still running |
| reconnecting… | The connection dropped and is being re-established |
| stream lost | Reconnection gave up. Use Reconnect or Refresh |
An app that is genuinely idle sits at streaming live with the count unchanged. That is not the same as stream lost, and the counter is what tells them apart.
When there is nothing to stream
Each empty case says something different, and the difference is the diagnosis.
| The tab says | What it means | What to do |
|---|---|---|
| No logs yet. Apps emit logs as they run | The pod is up and has written nothing | Exercise the app, or wait |
| The container is still building | There is no pod yet | Watch the Deploys tab for build progress |
| No pods running, naming the app's state | The app is not running at all | Check Deploys to see what happened |
| Could not resolve a pod for this app | The platform cannot find a pod to read | Check the app's status; if it reads running, refresh |
| Logs are unavailable for this app right now | The log source did not answer | Refresh. If it persists, the platform side is the problem, not your app |
| No lines match the current filter | You are filtering | Clear the filter |
| Failed to load logs, with the reason | The fetch itself failed | The message carries the platform's own reason |
The distinction between no logs yet and no pods running is the useful one. The first means your app is alive and quiet. The second means there is nothing alive to be quiet.
What these logs are and are not
This is the pod's own output: whatever your app writes to its standard output and standard error, plus whatever the framework writes on its behalf. It starts when the container starts.
It is not the build log. Cloning your repository and installing dependencies happen before this pod is serving, and that output lives with the deploy. When a deploy fails, the tab says so and points at Deploys rather than showing an empty stream.