Log
Know the component and how to use it.
Log allows the creation of log registers inside a pipeline. It helps in the generation of steps traceability when you want so.
The generated logs are available under Pipeline Logs in Monitor.
In addition, when you are building a pipeline and make tests in the Test mode area, the results are available on the LOGS tab, right next to MESSAGES, as shown below.
Take a look at the configuration parameters of the component:
- Step Name: defines the name of the component on canvas.
- Log Level: defines how the generated log will be classified (options: INFO, ERROR and WARN).
- Message: defines a message that will be registered in the log - it's possible to use the Double Braces functionality, that allows you to build a message com data from the pipeline flow).
Example:
There's been an error when trying to register the client code {{ message.id }}
IMPORTANT: all the line break characters (\n or \r\n) will be removed in the logs display.
The component accepts any input message and can use it through Double Braces.
The component doesn't change any information of the input message. Therefore, it' is returned to the following component or used as the final answer if this component is the last step of the pipeline.
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
IMPORTANT: 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