CLI · CommandsLogs & console

Logs & console

Stream logs and open an interactive console.

eqs logs <svc>

Streams the service's runtime logs (SSE).

-f, --followFollow in real time

--instance <n>Filter by instance

--since <dur>E.g.: 10m, 1h

shell

eqs logs web-frontend --follow

eqs exec <svc> [-- cmd]

Runs one command on an instance and exits with its status; with no command, opens an interactive shell (PTY).

--instance <n>Target instance

--stdinPipe this process's stdin to the command

--timeout <ms>Kill the command after this long (max 300000)

shell

eqs exec api-gateway -- npm run db:seed

eqs console <svc>

Interactive console over WebSocket (kubectl exec style).

shell

eqs console worker

Everything after -- is the command, passed as argv: nothing on either side re-splits it, so what you would quote at a terminal is what you quote here. Ask for a shell explicitly when you want one (sh -lc '…'). The exit status is the command's own, so && and set -e work around it — that is what makes a seed or a migration runnable from CI rather than only by hand. A command killed at the timeout exits 124. Pipe a file in with --stdin: eqs exec api --stdin -- psql -f - < schema.sql.