Read an environment's logs

The Logs tab on an environment is the record of everything strackt has done to it — deploys, configuration updates, rebuilds, rollbacks, restores, and commands. When you want to know what happened on a deploy, or why a change took a while, this is where you look.

Finding it

Open an application, pick the environment you care about from the switcher at the top, and choose Logs. You'll see the 25 most recent operations, newest first. Each row shows a status dot, what kind of operation it was, how it ended, when it started, and how long it took.

This is per-environment: production and staging each keep their own history, so switching environments switches the log you're reading.

Reading a step's output

Click any row to expand it in place. It opens to show that operation's individual steps and the output each one produced, as plain text. Nothing reloads — the detail is already there, so you can open and close rows freely while you scan.

What this does and doesn't show

The Logs tab is the most complete view of strackt's own work on the environment — broader than the deploy-only history elsewhere, because it includes configuration changes, rebuilds, and one-off commands too.

Two things it doesn't cover yet:

• Your application's own logs. This shows what strackt did — the deploy and setup steps — not your app's runtime output or web-server access logs.
• Live updates. The output for an operation that's still running appears when you reload the page, not as it streams.