Process Instances

Logging for the Process executions.

Basis to majority of Frends logging, Process Instances contain information what happened during a single integration execution. At top level the instances contain information about when Process was executed, did it succeed and how long it took, as well as any results of the execution.

Example view of Process Instance list.

Process Instance logs

You can view the Process execution and all its steps by opening any of the Process Instances from the list. On a default log level, all the results of each Process Task are logged into the Process Instance. This can be adjusted based on your needs to log more, including the input parameters for each Task and shape. Or less, to focus solely on erroneus executions, to save bandwidth, storage and performance for the actual execution.

Process executions can be viewed from the Process Instance list, including the steps in the Process.

With the Process Instance open, it's possible to click and view the logged values for each shape in the Process. This allows for easy debugging and fast development, as well as clear view to less technical personnel on what happened during each Process execution.

HTTP response for an API call shows the duration, response body as well as headers.

Sometimes it's also useful to get more details about an execution into the Process Instance list directly. Promoted values can be used to do exactly this during development of a Process. When a shape in the Process is set to promote the result, the value for that shape will be shown on the Process Instance list, and the executions can then be searched by that value.

A side effect of the promotion is that the value will always be logged in the Process Instance, regardless of the set log level, including input parameters. Promoted values can thus also be used as a debugging method even when the Environment as a whole would otherwise have reduced logging set.

Picture of Frends Process Editor, showing the advanced settings for a shape.
Advanced settings for shapes allow adjusting the logging behaviour for that shape alone.

As an opposite to promoted value, it's also possible to set a shape to skip logging result and parameters. This is useful for hiding sensitive information, such as passwords, authentication tokens and social security numbers from the logs. While it reduces the ability to debug errors for those shapes, it increases the security of Process Instance logs.

It can also have positive implications for the performance, in case the amount of data for the shape is large. Not logging all of the data can be beneficial in many ways. Under default log level settings, the maximum data size logged is limited to 100 array entries or 8192 characters of textual data.

How to access Process Instances?

Process Instances can be accessed through the Process list for each Process and for each Environment. You can find more information about how to read Process Instance logs from this guide: How to view integration logs.

Last updated

Was this helpful?