Log commands

The logs commands give you one way to read logs across the platform — pipeline builds, environment deployments (CloudFormation or Terraform), and Kubernetes app pods. They share a common set of flags for following, filtering, and bounding output.

All logs commands need a project id. Pass --project <id> or set MICROTICA_PROJECT_ID.

Common flags

Every logs subcommand accepts these:

Output and exit codes

By default the output is human-readable text — one line per entry as <timestamp> <severity> <source> <message> — with a one-line summary on stderr. Add --json (or --query) for NDJSON, where each line is a self-contained JSON object and the final line is an end marker carrying the normalized status.

The logs commands use richer exit codes than the rest of the CLI: 0 success, 1 CLI/API error, 2 the stream didn't end cleanly (interrupted, disconnected, or timed out), 3 the observed result was a failure. You can branch on the exit code instead of parsing output:

microtica logs deploy <envId> <deploymentId> --follow --timeout 30m \
  && echo "deploy OK" \
  || echo "deploy failed or dropped (exit $?)"

logs deploy

Stream the events of one environment deployment. The CLI picks the backend automatically from the environment's IaC tool: CloudFormation events for CFN environments, the realtime Terraform stream for Terraform environments.

# Tail a running deploy, give up after 20 minutes
microtica logs deploy <envId> <deploymentId> --follow --timeout 20m

# Just the failure events
microtica logs deploy <envId> <deploymentId> --failures-only --json

# Last 50 events only
microtica logs deploy <envId> <deploymentId> --tail 50

To find a deployment id, use pipeline history or env last-deploy.

logs build

Stream the per-step log output of a pipeline build.

# Watch a running build
microtica logs build <pipelineId> <buildId> --follow --timeout 20m

# Just the failing step, after the fact
microtica logs build <pipelineId> <buildId> --failures-only

# One step, grepping for a pattern
microtica logs build <pipelineId> <buildId> --step build --search "ENOENT" -i

By default, when a build step performs an environment deployment, its CloudFormation or Terraform events are stitched into the same stream alongside the step's output, each tagged with its source. Pass --no-stitch to see only the pipeline step's output.

--failures-only here skips steps that succeeded and marks failing steps' lines as errors. It can't be combined with --follow, since failure can't be known in real time.

logs app

Fetch the logs of a deployed app's pod. This is the same handler as the app logs alias.

# Latest snapshot of the app in one environment
microtica logs app <name> --env <envId>

# Grep for errors across the last 200 entries
microtica logs app <name> --env <envId> --tail 200 --search "panic|fatal|ERROR" -i

# Explicit cluster, namespace, and pod
microtica logs app <name> --cluster <clusterId> --namespace <ns> --pod <podName>

Next steps

• Output and exit-code conventions
• Trigger a build
• Deploy an environment