Waypoint Logs

Command: waypoint logs

Show log output from an application's current deployment

Usage

Usage: waypoint logs [options]

Show log output from all current deployments.

The logs will include output from deployments that aren't released. As new deployments are made, their logs will appear automatically.

The six character text after the date on a log line is the last six characters of the instance ID. This can be used to trace any logs back to a specific deployment or filter out certain log messages.

Global Options

-plain - Plain output: no colors, no animation. The default is false.
-app=<string> (-a) - App to target. Certain commands require a single app target for Waypoint configurations with multiple apps. If you have a single app, then this can be ignored.
-project=<string> (-p) - Project to target.
-workspace=<string> (-w) - Workspace to operate in.

Operation Options

-label=<key=value> - Labels to set for this operation. Can be specified multiple times.
-local - True to use a local runner to execute the operation, false to use a remote runner. If unset, Waypoint will automatically determine where the operation will occur, defaulting to remote if possible.
-remote-source=<key=value> - Override configurations for how remote runners source data. This is specified to the data source type being used in your configuration. This is used for example to set a specific Git ref to run against.
-var=<key=value> - Variable value to set for this operation. Can be specified multiple times.
-var-file=<string> - HCL or JSON file containing variable values to set for this operation. If any ".auto.wpvars" or ".auto.wpvars.json" files are present, they will be automatically loaded.

Command Options

-deployment-seq=<string> - Get logs for a specific deployment of the app using the deployment sequence number. Not valid with the -workspace param as deployment sequence numbers span across workspaces.