log.trace
The log.trace function writes a message to the Atmos log at the trace level. Use it for the finest-grained detail, such as each iteration of a loop or every value a script considers.
Usage
log.trace(message, **fields)
Arguments
messageRequired. Exactly one positional argument: the message, as a string. Passing more than one positional argument, or a value that is not a string, fails with an argument error.
**fields(Optional) Any number of keyword arguments, written to the log as structured key/value pairs after the message. Field names must be identifiers: letters, digits, and underscores, not starting with a digit. A value that is
None, a boolean, an integer, a float, or a string keeps its native type. Any other value, such as a list or dictionary, is logged using itsstr()form.
Returns
The return value is None. The call is a side effect and never becomes the step value.
Behavior
- The message goes to the Atmos logger, so it honors
--logs-level(orATMOS_LOGS_LEVEL) andlogs.file. Below the configured level, the call prints nothing. See logs configuration for the levels and the log destination. - Log output never goes to stdout, so it cannot change what
printoroutputproduce. - Every message carries a
stepfield: the step name for a workflow or custom command step, or the script path for a standalone script. - Inside
steps.paralleltasks, ataskfield names the running task, for exampletask=dev, ortask=grp/innerfor nested groups. A group with a single task adds notaskfield. - If you pass a field named
steportask, your value replaces the automatic one. - Secrets that Atmos knows about are masked in the message and in field values.