Logs

Lizard captures runtime logs, build logs, and the log tail around crashes. Stream them live in your terminal or browse them in the dashboard.

Lizard collects runtime logs while a log stream is open (lizard logs or the dashboard Logs page, plus 60 seconds after it closes), around deploys and restarts, and while a service is crash-looping. Opening a stream fills in the last 500 lines per replica.

Runtime logs

lizard logs                       # last 200 runtime lines, then live tail
lizard logs --service api         # a specific service
lizard logs --tail 1000           # print the last 1000 lines and exit (max 1000)
lizard logs --level error         # filter by level

Behavior with `--json`

lizard logs --json returns the last 200 lines (override with --tail N, max 1000) and exits. Use it for snapshots and scripting. A snapshot taken while nobody was streaming can miss recent lines; open a stream first if you need them.

Without a terminal (piped output, CI, an agent), lizard logs acts as if you passed --json: it prints the last 200 lines and exits. To follow logs live, run it in a terminal without --json.

Build logs

lizard logs --build               # the most recent build's logs

This is the first thing to check when a deploy fails: read it, fix the cause, then lizard redeploy. See Build Pipeline.

Restart / crash logs

When a replica crashes, Lizard saves the log tail around the crash. Manual restarts and variable changes appear in the list too, but have no tail.

lizard logs --restarts            # list recent restarts with their ids
lizard logs --restart <id>        # the log tail of one crash
lizard logs --restart latest      # the most recent event, which may be a manual restart

Paging through history

lizard service logs supports paging older windows:

lizard service logs --service api --tail all     # last 2,000 lines (no follow)
lizard service logs --service api --page 2       # older window (implies --tail 200)

Dashboard

The dashboard (lizard open) streams runtime and build logs with search and level filters. Open a service and click a deploy in its history to see that deploy’s build output.