Skip to main content

Configuring Trace Levels

Trace output verbosity is determined by the following sources, listed in order of precedence:

  1. Verbosity flags (-v/--verbose, -vv/--very-verbose). If these flags are provided, they override all other settings.
  2. The SPICED_LOG environment variable. This is used only if verbosity flags are not set
  3. The runtime.output_level YAML configuration file. This is used only if neither verbosity flags nor the environment variable are set.

Default​

The default trace level is INFO, suitable for general information about the system.

SPICED_LOG="task_history=INFO,spiced=INFO,runtime=INFO,secrets=INFO,data_components=INFO,cache=INFO,extensions=INFO,spice_cloud=INFO,llms=INFO,reqwest_retry::middleware=off,WARN"

The equivalent runtime.output_level configuration is info:

runtime:
  output_level: info

Enabling Debug Mode​

Use the -v/--verbose CLI flags to enable detailed logs, useful for debugging.

spice run -v
spiced -v

Alternatively you can use runtime.output_level yaml configuration:

runtime:
  output_level: verbose

This sets SPICED_LOG to DEBUG level:

SPICED_LOG="task_history=DEBUG,spiced=DEBUG,runtime=DEBUG,secrets=DEBUG,data_components=DEBUG,cache=DEBUG,extensions=DEBUG,spice_cloud=DEBUG,llms=DEBUG,DEBUG" spice run

Enabling Trace Mode​

Use the -vv/--very-verbose CLI flag to enable the most detailed logs, typically for in-depth troubleshooting.

spice run -vv
spiced -vv

Alternatively you can use runtime.output_level yaml configuration:

runtime:
  output_level: very_verbose

This sets SPICED_LOG to TRACE level:

SPICED_LOG="task_history=TRACE,spiced=TRACE,runtime=TRACE,secrets=TRACE,data_components=TRACE,cache=TRACE,extensions=TRACE,spice_cloud=TRACE,llms=TRACE,TRACE" spice run

Granular Configuration​

For specific component trace configuration, adjust the trace levels as needed:

SPICED_LOG="spiced=INFO,runtime=DEBUG,data_components=WARN,cache=WARN" spice run