EN-US
Ask or search…
K
Links

Log

Discover more about the Log component and how to use it on the Digibee Integration Platform.
Log allows the creation of log registers within a pipeline. It helps with the creation of step traces.
When you are building a pipeline and testing in the Execution panel area, the results are displayed on the Logs tab.
​The generated logs are also available under Pipeline Logs in Monitor.

Parameters

Take a look at the configuration options for the component. Parameters supported by Double Braces expressions are marked with (DB).
Parameter
Description
Default value
Data type
Log Level
How the generated log will be classified. The options are: Info, Error, and Warn.
ERROR
String
Message (DB)
Message that is entered in the log. It's possible to use the Double Braces, which allows you to create a message with data from the pipeline flow (example: “There's been an error when trying to register the client code {{ message.id }}”)
Error processing message {{ message.$.myField }}
String
All the line break characters (\n or \r\n) will be removed in the logs list.

Messages flow

Input

The component accepts any input message and can use it through Double Braces.

Output

The component doesn't change any information of the input message. Therefore, the message returns to the following component or is used as the final answer if this component is the last step of the pipeline.

Sensitive Fields

When sensitive fields are configured in the pipeline or in your realm, these fields will appear in the component output obfuscated with the "***" character set.
Example:
Imagine that the sensitive field “email” is defined in the pipeline and the Log component message is configured as follows:
There was an error sending email to {{message.email}} on {{message.dateTime}}
The log will be presented as follows:
There was an error sending email to *** on 05/07/2021 10: 11: 33: 5120
​Obfuscation of sensitive fields requires more processing resources and memory in the pipeline. These additional features are affected by both the number of sensitive fields configured and the size of the message.
Last modified 2mo ago