logs
Show what an application printed.
read onlyrepeatableruns until stopped
What a running application printed, as text, one line per line, so it can go
straight into grep or a file.
This is the application, not the build. What a build wrote is outplane deploy logs. With no application named it covers the whole team, and --follow keeps
printing until you stop it.
Usage
outplane logs [APP] [flags]Arguments
| Argument | Type | Description |
|---|---|---|
APP | string | Application name or id. Omit for the whole team. |
Flags
| Flag | Type | Description |
|---|---|---|
--since | duration | How far back to look. Defaults to 1h. |
-n, --lines | int | How many of the most recent lines to show. Defaults to 200. |
-f, --follow | bool | Keep printing new lines until interrupted. |
--search | string | Only lines containing this text, case-insensitive. |
--level | string | Only lines that look like this severity. Repeatable is not supported; pass the lowest you want. One of error, warning, info, debug, trace. |
--timestamps | bool | Prefix each line with the time it was written. |
The global flags apply as well.
Examples
The last hour, for every application in the team
outplane logsFollow one application
outplane logs checkout --followErrors from the last day, with times
outplane logs checkout --since 24h --level error --timestampsWhat to Know
- Output is the log text on stdout, one line per line, so it can be piped into grep or a file. It is not JSON, and --json does not change that: a log line has no fields to report.
- --level narrows by the words in the line, because severity is not recorded separately. It can miss a line that phrases its severity differently, and asking for info applies no filter at all, since info is the absence of the other keywords.
- --lines counts from the most recent, so raising it reaches further back rather than adding newer lines.
- Without --follow the command returns what exists now and exits 0, even when that is nothing. An application that has printed nothing is not an error.
- --follow ends only on interruption, and exits 130 when it is. It never decides the application is finished.
- This is the running application. Build output is
outplane deploy logs.
Errors
Beyond 0 for success, this command exits with:
| Exit | Kind | Meaning |
|---|---|---|
2 | usage | Invalid arguments, unknown flag, or client-side validation failure. |
3 | auth | Not authenticated, token revoked or expired, or forbidden for this team. |
5 | not_found | The named resource does not exist, or is not visible to this credential. |
8 | upstream | The Out Plane API returned a server error. |
130 | interrupted | Cancelled by the user. |
The code on the error object is one of logs.no_team_slug, app.not_found, usage.bad_level, usage.empty_argument, logs.bad_response. Branch on that, or on the exit status. The message is prose and changes.