Appearance
Log
Writes an entry to the flow log for each record that passes, with a fixed message, the chosen severity and the record and its metadata attached, then forwards the record unchanged. Use it to trace what goes through a branch or to log errors from error pins.
Pins
| Pin | Kind | Types | Description |
|---|---|---|---|
| Input | input | any | Record to log. |
| Output | output | same as input | The unchanged record, forwarded after logging. |
Configuration
| Field | Type | Default | Description |
|---|---|---|---|
LogLevel | dropdown: 1 VERBOSE, 2 DEBUG, 3 INFO, 4 WARN, 5 ERROR, 6 FATAL | 3 | Severity of the log entry. |
LogMessage | string (text editor) | Required. The message text, written as is (no placeholders). | |
NoTruncation | boolean | false | true: long property values of the attached record and metadata are not shortened. |
Behaviour
- For each record one log entry is written with: the message, the severity, the flow id and name, the component, the record (serialized to JSON, with its record id) and the metadata (serialized to JSON, with correlation and session id). Then the record is sent to
Output. - By default long values in the attached JSON are truncated;
NoTruncation=truekeeps them complete. - On start, if
LogLevelis lower than the flow's log level, an indicator and a warning tell you that the entries will not be visible.
Notes
- The message is static; the record content is visible in the attached data of the log entry. To log a computed text, build it with a script component before the Log.
- Logging large records with
NoTruncation=trueon every message can produce very large logs. - Avoid logging records that contain secrets (passwords, tokens); they are stored in the log as JSON.
Example
json
{ "LogLevel": 5, "LogMessage": "Order import failed", "NoTruncation": false }Http client Error → Log → ...