---
title: pulumi logs | CLI commands
url: /docs/iac/cli/commands/pulumi_logs/
---

Show aggregated resource logs for a stack

## Synopsis

[EXPERIMENTAL] Show aggregated resource logs for a stack

This command aggregates log entries associated with the resources in a stack from the corresponding
provider. For example, for AWS resources, the `pulumi logs` command will query
CloudWatch Logs for log data relevant to resources in a stack.

```
pulumi logs [flags]
```

## Options

```
      --config-file string   Use the configuration values in the specified file rather than detecting the file name
  -f, --follow               Follow the log stream in real time (like tail -f)
  -h, --help                 help for logs
  -j, --json                 Emit output as JSON
  -r, --resource string      Only return logs for the requested resource ('name', 'type::name' or full URN).  Defaults to returning all logs.
      --since string         Only return logs newer than a relative duration ('5s', '2m', '3h') or absolute timestamp.  Defaults to returning the last 1 hour of logs. (default "1h")
  -s, --stack string         The name of the stack to operate on. Defaults to the current stack
```

## Options inherited from parent commands

```
      --color string                 Colorize output. Choices are: always, never, raw, auto (default "auto")
  -C, --cwd string                   Run pulumi as if it had been started in another directory
      --disable-integrity-checking   Disable integrity checking of checkpoint files
  -e, --emoji                        Enable emojis in the output
  -Q, --fully-qualify-stack-names    Show fully-qualified stack names
      --logflow                      Flow log settings to child processes (like plugins)
      --logtostderr                  Log to stderr instead of to files
      --memprofilerate int           Enable more precise (and expensive) memory allocation profiles by setting runtime.MemProfileRate
      --non-interactive              Disable interactive mode for all commands
      --otel-traces string           Export OpenTelemetry traces to the specified endpoint. Use file:// for local JSON files, grpc:// for remote collectors
      --profiling string             Emit CPU and memory profiles and an execution trace to '[filename].[pid].{cpu,mem,trace}', respectively
      --tracing file:                Emit tracing to the specified endpoint. Use the file: scheme to write tracing data to a local file
  -v, --verbose int                  Enable verbose logging (e.g., v=3); anything >3 is very verbose
```

## SEE ALSO

* [pulumi](/docs/iac/cli/commands/pulumi/)	 - Pulumi command line
* [pulumi logs decrypt](/docs/iac/cli/commands/pulumi_logs_decrypt/)	 - Decrypt and display automatic logs