Blender CLI Logging and Render Farm Log Integration: Adding Timestamps for Failure Diagnosis

When running Blender in background mode on a render farm, each node writes its console output to a log file via the --log option to aid in post‑mortem analysis of failed deployments. The default log lacks timestamps and uses plain‑text formatting without structured fields, which complicates correlation with external monitoring tools and automated parsing for alerting.

To improve diagnosability, one must decide how to augment the log with reliable time metadata or a machine‑readable format while keeping verbosity low enough to avoid filling node disks and without requiring changes to Blender’s core logging subsystem.

What mechanisms can be used to add timestamps or structured data to Blender’s log output? Can the existing --verbose flag be leveraged for sequential numbering that approximates timing, or is a wrapper script that prepends ISO‑8601 stamps necessary? Should log rotation or size limits be enforced centrally to manage growth when higher verbosity is enabled?