Monitoring Commands

logs

Stream logs from a Service of an application.

$ convox cloud logs -a <app> -i <machine> --service <service>

--service is required on a Cloud machine. Without it, the command fails with logs must specify --service.

Options:

--allow-previous: Include previous container logs
--filter: Has no effect on a Cloud machine, because --service is required and --filter is ignored with --service
--max-log-requests: Maximum number of concurrent log follow streams (default 20). Raise it to follow a Service that runs more Processes than that
--no-follow: Don't stream logs
--service: Service to read logs from (required)
--since: Time window (e.g., "2h", "30m"; default "2m")
--tail: Number of lines to read from the end of each Process's log

With CLI 3.25.12 or later, a --no-follow read that ends before the end of its output prints what it received, then ERROR: log stream ended before the end of output, and exits 1. A complete read exits 0, so scripts can tell a complete read from a cut one.

Example:

$ convox cloud logs -a myapp -i production --service web --since 1h
[pod/web-7cd6cc78dd-blvtn/myapp] 2026-01-15T10:30:00.123456789Z GET / 200
[pod/web-7cd6cc78dd-blvtn/myapp] 2026-01-15T10:30:15.482913004Z GET /api/users 200

Each line starts with the Process that wrote it, [pod/<process>/<app>], and its timestamp. See logs for how a Service's logs are read.

Monitoring Commands

logs

Stream logs from a Service of an application.

$ convox cloud logs -a <app> -i <machine> --service <service>

--service is required on a Cloud machine. Without it, the command fails with logs must specify --service.

Options:

--allow-previous: Include previous container logs

--filter: Has no effect on a Cloud machine, because --service is required and --filter is ignored with --service

--max-log-requests: Maximum number of concurrent log follow streams (default 20). Raise it to follow a Service that runs more Processes than that

--no-follow: Don't stream logs

--service: Service to read logs from (required)

--since: Time window (e.g., "2h", "30m"; default "2m")

--tail: Number of lines to read from the end of each Process's log

Example:

$ convox cloud logs -a myapp -i production --service web --since 1h [pod/web-7cd6cc78dd-blvtn/myapp] 2026-01-15T10:30:00.123456789Z GET / 200 [pod/web-7cd6cc78dd-blvtn/myapp] 2026-01-15T10:30:15.482913004Z GET /api/users 200

Each line starts with the Process that wrote it, [pod/<process>/<app>], and its timestamp. See logs for how a Service's logs are read.