Watch your application's logs live

The Logs page streams what your application is printing right now — its own output, background jobs, scheduled tasks, and web requests — without SSHing into a server or opening a file. When you're chasing a bug and want to see the effect as you trigger it, this is where you watch.

Opening it

Open an application, pick the environment you care about from the switcher at the top, and choose Logs. It opens streaming live: the last 15 minutes of output appear first, then new lines are added as they arrive. The footer reads Streaming live with a running line count so you know it's connected.

Logs are per-environment — production and staging each have their own stream, and switching environments switches what you're watching.

In a hurry, or on another page? Press ⌘K, choose Tail logs, and a compact live tail opens in an overlay over whatever you're looking at — no navigating away. Press ↵ (or Open full Logs) to jump to the full page, or Esc to close.

Focusing on one part of your app

By default you see everything. The channel chips along the top narrow it down:

| Channel | Shows | |---|---| | All | Everything below, together (the default) | | Runtime | Your application's own log output | | Queue | Background jobs and queue workers | | Scheduler | Scheduled tasks | | PHP | Low-level PHP process logs | | HTTP | Incoming web requests — method, path, status, and how long each took |

HTTP is high-volume, so it isn't in the default view — pick it when you want to watch traffic hit your app. It shows the request method, path, response status, and duration, with no query strings, client addresses, or headers.

Above the stream, the Search box filters what's currently on screen to lines that match — handy for isolating one request ID or error message in a busy stream. It filters what you can already see; it doesn't fetch older lines.

Following, or pausing to read

While the stream is live it auto-scrolls to the newest line. Two controls let you read without losing your place:

• Follow keeps the view pinned to the latest output as it arrives.
• Pause freezes the view so you can read something that would otherwise scroll away. New lines keep collecting in the background — press Resume to catch up.

Live output runs a few seconds behind real time. That's the normal delay for logs to travel from the server to strackt, not a sign anything is stuck. If the connection drops, the footer shows Reconnecting… and picks back up on its own.

Looking a little further back

The Logs page is built for the live moment, but you don't have to catch things as they happen. The range control switches between Live, the last 1h, and the last 24h. The two history ranges load a fixed window and hold still — Follow and Pause don't apply there, since nothing is streaming. Switch back to Live to resume the running tail.

Logs vs. Activity

There are two "what happened" views on an environment, and they answer different questions:

• Logs (this page) is your application's output — what your code, jobs, and requests are printing, live.
• Activity is strackt's record of what it did to the environment — deploys, configuration updates, rebuilds, rollbacks, restores, and commands, with the step-by-step output of each. It's history, not a live stream.

If you're asking "what is my app doing right now," use Logs. If you're asking "what did that deploy do, and why did it take a while," use Activity.

Good to know

• Logs start from when your environment got its current setup. strackt begins collecting an environment's output once it's running on a server, so you won't see anything from before then.
• A quiet stream isn't a broken one. If nothing's showing, your app may simply not be printing anything right now. Trigger the behaviour you're investigating and watch the lines appear.
• Prefer the terminal? The same live stream is available from the command line with strackt env:logs --follow — see View your application logs.