Logs

Reading an app's logs needs apps/readLogs. It is a data action, held by Reader, Contributor, Owner, Apps Operator, Platform Contributor and Platform Owner — not by Apps Reader or Platform Reader.

In the portal

Open the app and its Logs tab. Container Logs shows what the app's instances write to standard output and standard error, starting with the last 500 lines of each and then live. The tab keeps the newest 1,000 lines; Download saves those.

• Pod — follow All pods or one instance; shown when the app has more than one.
• Pause and Resume, Download and Clear; Auto-scroll keeps the newest line in view.
• When the connection drops, the tab tries again up to five times, three seconds apart, and then offers Retry.

A slot's logs are on the slot's page. Build output is not here but in each deployment's build log — see Build logs.

With the CLI

stsh apps logs my-app -g my-resource-group
stsh apps logs my-app -g my-resource-group --pod <pod>
stsh apps slot logs my-app staging -g my-resource-group

The command follows the logs until you interrupt it. stsh apps pods my-app lists the instances by name, for --pod.

When there are no logs

Logs come from instances that run. A stopped app, or one whose instances have not started — for example while a secret cannot be read — has none to show; its status and the Operations tab say why — see Statuses.