SaltDebugPrint¶
Utility node that logs a readable representation of the input value and its type to the debug console, tagged with a user-provided label. The input value is passed through unchanged, allowing inline inspection within workflows.
Usage¶
Use this node to inspect data flowing through your workflow at specific points. Connect any value to 'value' and provide a short 'label' to identify the log entry. The node will log the value’s structure/type and forward the value so downstream nodes continue to operate normally.
Inputs¶
| Field | Required | Type | Description | Example |
|---|---|---|---|---|
| value | True | WILDCARD | The value to be inspected and logged. Supports arbitrary types including numbers, strings, lists, tuples, dicts, and tensors. | 42 |
| label | True | STRING | A short label to identify this debug output in logs. | After normalization |
Outputs¶
| Field | Type | Description | Example |
|---|---|---|---|
| value | WILDCARD | The original input value, unchanged, allowing continued use in the workflow. | 42 |
Important Notes¶
- Pass-through behavior: The node never modifies the input value; it only logs and returns it.
- Logging level: Output is written at debug level. If debug logging is disabled, you may not see messages.
- Representation details: Containers (lists, tuples, dicts) are logged recursively; strings are quoted; basic scalars are printed directly; tensors are summarized by shape (e.g., Tensor[1, 3, 256, 256]) rather than full contents.
- Label usage: The label appears in the log prefix to help identify where the message originated.
- Error handling: If logging or formatting fails, the node still returns the original value.
Troubleshooting¶
- No output visible: Ensure the system's debug logging is enabled. Without debug level logging, messages will not appear.
- Logs are too verbose: Reduce usage of this node or tighten logging level to info/warn in your environment.
- Large or complex values slow logging: Logging very large nested structures can be slow. Consider sampling or placing fewer debug points.
- Cannot distinguish multiple logs: Use unique, descriptive labels per placement to make entries easy to identify.