reoclo logs

reoclo logs tail [options]

reoclo logs tail streams or fetches recent log lines from a server source. The runner forwards logs from containers, the system journal, the Docker daemon, and itself.

Options

Flag	Default	Description
--server <idOrName>	required	Server to tail logs from.
--source-type <type>	container	One of container, system, docker_daemon, runner, kernel, auth.
--source-name <name>	(varies)	Container name (for container) or unit name (for system).
--tail <n>	100	Initial number of lines to fetch.
--follow	off	Stream new lines as they arrive.
--search <term>	none	Substring filter applied server-side.
--level <level>	all	debug, info, warn, error.
--from <ts>	recent	RFC 3339 timestamp; only return lines after this time.
--to <ts>	none	RFC 3339 timestamp; only return lines before this time.

Examples

Tail the last 200 lines from a container:

reoclo logs tail --server prod-web-1 --source-type container --source-name api --tail 200

Follow live logs from the systemd journal:

reoclo logs tail --server prod-web-1 --source-type system --source-name reoclo-runner --follow

Search recent logs for a request ID:

reoclo logs tail --server prod-web-1 --source-name api --tail 1000 --search req_abc123

Filter by level for a time window:

reoclo logs tail --server prod-web-1 \
  --source-name api --level error \
  --from 2026-04-25T00:00:00Z --to 2026-04-25T01:00:00Z

Output formats

The default is plain text, suitable for grep, less, and tail -f-style consumption. Use -o json for structured output that includes timestamps, source metadata, and parsed levels:

reoclo logs tail --server prod-web-1 --source-name api --tail 50 -o json | jq '.timestamp + " " + .message'

Exit codes

Code	Meaning
0	Success
1	Network, runner, or upstream log query failure
2	Bad arguments (e.g. invalid --from timestamp)
3	Authentication failure
5	Server or source not found

Related

• reoclo deployments logs — build-stage logs for one deployment
• reoclo servers — list available servers