Logs

Execution records contain essential information to track, debug, and audit the execution of an integration flow.

You can view the following execution records in Sensedia Analytics.

• Request of the REST type trigger.

• Request and response of:

  • Connectors
  • Choice
  • For Each
  • JSON Transformation

Common fields

See below the components that exist in all execution records, regardless of the type of step being executed:

• runtimeExecutionId: unique identifier referring to the integration flow execution time. Helps to track and monitor the execution instance.

• executionId: execution identifier. Can be used to track individual executions within an execution session.

• integrationFlowId: unique identifier of the integration flow.

• integrationFlowName: name of the integration flow.

• integrationFlowVersion: version of the integration flow being executed.

Variable fields

Now, see the components that vary according to the type of step being executed:

• name: name of the integration flow step being executed.

• tag: tag associated with the step, indicating its nature (request, response, input, or output).

• message: contains a JSON string with detailed information about the step. This component is especially useful for understanding the content and context of the step.

Examples

REST type trigger

Here we have a POST request. The message field provides a JSON string with the request body, path, method, and headers.

Connectors

Request

In the example below, we have the execution of the "Get_Product_List" step of "Flow 1" (version 1.0). During this execution, a request was made using the GET method to an endpoint.

Response

The example below provides information about the execution of the "Get_Description" step, including details about the response received and its status.

Choice

The example shows information about the execution of the Choice step, including relevant identifiers and metadata. The message indicates that currently the restaurant is offline and that there is an error regarding an invalid or expired token.

For Each

The For each step is processing a list of products, and this record captures the input of one of these products. Each product in the list is represented by a JSON object, which contains the details of a specific product: product ID, product type, creation date, etc.

NOTE

The message was shortened for example purposes.

JSON Transformation

The JSON Transformation step is processing street information, and this record captures the data input. The message brings information such as ZIP code, neighborhood, state, etc.

In the data output, we see the transformed JSON message: