Skip to main content

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 readsWhat it means
streaming liveConnected. Lines appear as the app writes them
pausedYou pressed Pause. The stream is still running
reconnecting…The connection dropped and is being re-established
stream lostReconnection 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 saysWhat it meansWhat to do
No logs yet. Apps emit logs as they runThe pod is up and has written nothingExercise the app, or wait
The container is still buildingThere is no pod yetWatch the Deploys tab for build progress
No pods running, naming the app's stateThe app is not running at allCheck Deploys to see what happened
Could not resolve a pod for this appThe platform cannot find a pod to readCheck the app's status; if it reads running, refresh
Logs are unavailable for this app right nowThe log source did not answerRefresh. If it persists, the platform side is the problem, not your app
No lines match the current filterYou are filteringClear the filter
Failed to load logs, with the reasonThe fetch itself failedThe 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.

Describes the platform as of .

Was this page helpful?