--- title: Logs description: Querying logs documentId: ipaas-logs locale: en-US --- 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. ```json { "runtimeExecutionId": "BD4E80522608F3F-0000000000000000", "executionId": null, "integrationFlowId": "1120e125-4faf-4c27-8418-ea82d5b857ad", "integrationFlowName": "Test e2e Choice v2", "integrationFlowVersion": "1.0.0", "name": "REST_Trigger", "tag": "Request", "message": { "body": "{\"teste\": \"just a test\"}", "path": "1b277a28726f", "method": "POST", "headers": { "Accept": "*/*", "X-Request-Id": "e7dd7de8-16cc-410e-afb7-7ef1550dbba4", "User-Agent": "PostmanRuntime/7.29.4", "X-Forwarded-Proto": "http", "X-Request-Start": "t=1717180375.285", "Host": "deploy-b233cf36-0b6b-4eac-9911-1b277a28726f.a1b2c3d4e5.integrations-tst.sensedia-eng.com", "Accept-Encoding": "gzip, deflate, br", "K-Proxy-Request": "activator", "Forwarded": "for=186.209.2.69;proto=http, for=10.251.183.82", "X-Forwarded-For": "186.209.2.69, 10.251.183.82, 10.251.171.244", "Postman-Token": "a44f3ed7-8c57-4f4a-9443-b07e774a6864", "Content-Length": "28", "Content-Type": "application/json", "X-Envoy-External-Address": "186.209.2.69" } } } ``` ### 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_. ```json { "runtimeExecutionId": "EA66FA90FBEA138-0000000000000004", "executionId": null, "integrationFlowId": "3333440d-0897-4346-aeb3-ad1d7f6a74fc", "integrationFlowName": "Flow 1", "integrationFlowVersion": "1.0", "name": "Get_Product_List", "tag": "Request", "message": { "url": "https://api-url.com", "path": "/Product", "method": "GET" } } ``` #### Response The example below provides information about the execution of the "Get_Description" _step_, including details about the response received and its status. ```json { "runtimeExecutionId": "EA66FA90FBEA138-0000000000000004", "executionId": null, "integrationFlowId": "3333440d-0897-4346-aeb3-ad1d7f6a74fc", "integrationFlowName": "Flow 1", "integrationFlowVersion": "1.0", "name": "Get_Description", "tag": "Response", "message": { "payload": { "@odata.context": "../$metadata#ProductDescription", "@odata.metadataEtag": "W/\"20240421022725\"", "value": { "@odata.etag": "W/\"SADL-201610170000000000000C~20161017000000.0000000\"", "SAP__Messages": [] } }, "status": 200 } } ``` ### 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. ```json { "runtimeExecutionId": "BD8894B984F316D-0000000000000000", "executionId": null, "integrationFlowId": "92324ecb-89ff-4ada-bb7c-80afbcd8ae13", "integrationFlowName": "Query Tables Choice EVH", "integrationFlowVersion": "1.0", "name": "Choice", "tag": "Input", "message": { "payload": "{StatusEstabelecimentoResult={Erros=[\"Invalid or expired token.\"], Online=false}}" } } ``` ### 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. ```json { "runtimeExecutionId": "EA66FA90FBEA138-0000000000000004", "executionId": null, "integrationFlowId": "3333440d-0897-4346-aeb3-ad1d7f6a74fc", "integrationFlowName": "Flow 1", "integrationFlowVersion": "1.0", "name": "For_Each_Product", "tag": "Input", "message": { "input": "[{ \"@odata.etag\": \"W/\\\"SADL-201610170000000000000C~20161017000000.0000000\\\"\", \"Product\": \"21\", \"ProductType\": \"SERV\", \"CreationDate\": \"2016-10-17\", \"CreationTime\": \"00:00:00\", \"CreationDateTime\": \"2016-10-17T00:00:00Z\", \"CreatedByUser\": \"CB9980000160\", \"LastChangeDate\": null, \"SAP_Messages\": [] }]" } } ``` 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. ```json { "runtimeExecutionId": "635812E1B03F2FA-0000000000000000", "executionId": null, "integrationFlowId": "4fda2927-54dd-4c82-a9bd-de161f59dd13", "integrationFlowName": "CEP Choice Json Transf", "integrationFlowVersion": "1.0", "name": "Json_Transf_2", "tag": "Input", "message": { "payload": "{ cep=13086-510, siafi=6291 }" } } ``` In the data output, we see the transformed JSON message: ```json { "runtimeExecutionId": "635812E1B03F2FA-0000000000000000", "executionId": null, "integrationFlowId": "4fda2927-54dd-4c82-a9bd-de161f59dd13", "integrationFlowName": "CEP Choice Json Transf", "integrationFlowVersion": "1.0", "name": "Json_Transf_2", "tag": "Output", "message": "Sensedia's headquarters is located at Rua Doutor Ricardo Benetton Martins, Polo II de Alta Tecnologia neighborhood (Campinas), in the best city: Campinas" } ```