pulumi insights account scan log | CLI commands

[EXPERIMENTAL] Retrieve log output for an Insights scan

Synopsis

[EXPERIMENTAL] Retrieve log output for an Insights scan.

By default, a single page of log entries is returned. Use –count to request more, or –all to fetch every entry.

Passing –job switches to step mode and returns the raw text output of a single step. –step selects the step within the job, and –all fetches the full step output.

pulumi insights account scan log <account> <scan-id> [flags]

Examples

  # Show the first page of a scan's logs.
  pulumi insights account scan log prod-aws scan-123

  # Show the last 100 entries.
  pulumi insights account scan log prod-aws scan-123 --count 100

  # Fetch every entry as JSON.
  pulumi insights account scan log prod-aws scan-123 --all --output json

  # Read step 0 of job 0 in full.
  pulumi insights account scan log prod-aws scan-123 --job 0 --step 0 --all

Options

      --all             Fetch every entry (mutually exclusive with --count)
      --count int       Number of log entries to display
  -h, --help            help for log
      --job int         Switch to step mode and select this job index (combine with --step)
      --org string      Organization that owns the Insights account (defaults to the current default org)
      --output string   Output format. Supported values are: default and json (default "default")
      --step int        Step index within --job whose log output to fetch

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 insights account scan - [EXPERIMENTAL] Trigger a resource discovery scan for an Insights account