Each log level includes all higher-severity levels. Setting log_level to warn logs system, error, and warn, but excludes info, debug, trace, and spam.
The following examples show representative log entries at each severity level. Each event in Platform is logged at one appropriate level based on its significance and purpose.
Critical platform lifecycle events such as initialization and shutdown.
Standard format (log_format_json=false):
Structured JSON format (log_format_json=true):
Unrecoverable errors that prevent operations from completing, such as missing required services or failed connections.
Standard format:
Structured JSON format:
Recoverable issues that require attention but don’t prevent operations from completing, such as duplicate modules or deprecated configurations.
Standard format:
Structured JSON format:
Normal operational events that track the progress of operations, such as module discovery completion and workflow execution milestones.
Recommended for production: The info level is the recommended default for production environments.
Standard format:
Structured JSON format:
Detailed diagnostic information useful for troubleshooting, including internal state changes and configuration details.
Standard format:
Structured JSON format:
Step-by-step execution flow including function entry/exit and variable values.
Performance impact: The trace level generates significant log volume and should only be used temporarily for troubleshooting specific issues.
Highest verbosity with extremely frequent events such as loop iterations and polling.
Not recommended: The spam level generates excessive log volume and is generally not recommended for any environment.