log
Emits a structured log line. message is a JSONLogic expression (a plain string
is valid), and fields attaches more JSONLogic-derived key/values.
Synopsis
{
"name": "log",
"input": {
"message": "Order processed",
"level": "info",
"fields": {
"order_id": {
"var": "data.order.id"
}
}
}
}
Description
log is an engine built-in from dataflow-rs. Orion declares no input schema for it, so a mistake in input surfaces when the task runs rather than when the workflow is saved.
Retry safety: pure. An engine built-in reads and writes the message and nothing else.
Fields
| Field | Type | Required | Default | Description |
|---|---|---|---|---|
message | JSONLogic | yes | — | The log message (string literal or expression) |
level | string | no | "info" | trace | debug | info | warn | error |
fields | object | no | {} | Map of name → JSONLogic expression, logged as structured fields |
Examples
{
"name": "log",
"input": {
"level": "info",
"message": "Order processed",
"fields": { "order_id": { "var": "data.order.id" } }
}
}
Related
- Workflows: the pipeline model these functions run in.
- Author a workflow: conditions, mapping and validation in practice.
- Task functions: the whole catalogue, and each function’s retry safety.
- Workflow definition: the data context every function reads and writes.
Last verified 14 September 2026