View your application logs

strackt env:logs shows what your application is logging on the server — without SSHing in or hunting through files. Run it for a quick look at the last hour, or follow the output live while you reproduce a problem.

See recent logs

strackt env:logs

That prints the last hour of output for your default environment. To pick another environment, or a different time window:

strackt env:logs --env staging
strackt env:logs --since 30m
strackt env:logs --since 7d

--since accepts windows like 30m, 2h, or 7d.

Follow logs live

Add --follow to stream new lines as they happen — useful while you trigger the behaviour you're investigating:

strackt env:logs --follow

Press Ctrl-C to stop. Live output is 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.

Narrow to one part of your app

By default you see everything. Use --channel to focus on one area:

strackt env:logs --channel queue

| Channel | Shows | |---|---| | runtime | Your application's own log output | | queue | Background job and queue worker output | | scheduler | Scheduled task output | | php | Low-level PHP process logs | | http | Incoming web requests — method, path, status, and how long each took |

strackt env:logs --channel http

HTTP request logs are high-volume, so they're kept out of the default view — ask for them with --channel http when you want to watch traffic hit your app. They show the request method, path, response status, and duration, with no query strings, client IPs, or headers.

Machine-readable output

For piping into other tools, --json prints one log entry per line as JSON:

strackt env:logs --json
strackt env:logs --follow --json

Good to know

• Logs start from when your environment got its current configuration. strackt begins collecting an environment's logs once it's set up on the server, so you won't see output from before then.
• Live output lags real time by a few seconds. That's the delivery delay, not a stalled stream.
• If you see a permission message, your access token doesn't include log access. Create or update a token with the logs permission in the dashboard, then run the command again.