lizard logs
Stream a service’s runtime logs, the last 200 lines followed by a live tail. For runtime logs without -s, logs does not use the linked service: on a TTY it asks which service to show, otherwise it shows all services in the project. --build and --restarts use the linked service.
Usage
lizard logs [flags]Flags
| Flag | Description |
|---|---|
--build | Show build logs instead |
--tail <n> | Print the last N lines (max 1000) and exit |
-l, --level <level> | Runtime logs at this level only: error, warn, info, or debug |
--restarts [n] | List the last N restarts (default 20) |
--restart <id> | Logs around a specific restart (latest for the most recent) |
-s, --service <id> | Service |
-p, --project <id> | Project name, slug, or ID |
With --json, lizard logs is not a stream — it returns the last 200 lines (override with --tail N, max 1000) and exits. Use it for snapshots and scripting; stream live only without --json.
Examples
Tail runtime logs
lizard logsTail logs for a specific service
lizard logs --service apiGet more history
lizard logs --tail 1000Filter by log level
lizard logs --level errorCheck the most recent build
lizard logs --buildInspect a crash or restart
lizard logs --restarts
lizard logs --restart latest
lizard logs --restart <id>See also
- Logs — runtime, build, and restart log behavior, plus paging through history with
lizard service logs - Incomplete Dockerfile — diagnosing a failed build from
lizard logs --build - lizard events — deploy history and replica status
- Deploy from Claude Code — the log commands an agent runs to check a deploy
Updated