Connector Logs
Introduction
Automation logs help to monitor the automation processes and troubleshoot any issues within your connector. When connectors trigger and automate actions, they generate logs that record each step taken.This allows you to maintain complete visibility into your connector’s performance, understand the data being processed, and identify any errors that may arise during execution.
To access connector's automation logs :
Click on More menus -> Automation -> Logs
In the Logs, you can see two types of logs Execution logs and Http logs:
(See the below picture)
Execution Logs
Execution Logs are created every time a connector is triggered.These logs track the execution of each step in the connector when the connector is triggered. They allow you to track the complete flow of the connector.It provides information on whether each action was successful or if any issues occurred, what actions were taken, when they happened.
In execution log tab you can see log id,connector name,received time,details. (See the below picture)
Log ID: A unique number to identify each log.
Connector Name: The name and ID of the connector that was triggered.
Received Time: The exact time the connector was triggered and logged.
Details:-
View log details :Clicking this opens a Log details pop-up with three tabs.(See the below picture)
Request JSON Tree: Shows the data that was sent or received during the request.
Log Information includes key details such as the connector name, received time, request headers, request body, and response body.
Execution Info: Shows step-by-step details of each action performed by the connector, including if each step was successful or if any errors occurred.
View Execution Info: This shows the execution information of each step in the connector.(See the below picture)
HTTP Logs
HTTP Logs logs capture details about any HTTP requests happening in the connector, specifically those initiated from the HTTP step. They are generated whenever a connector makes an HTTP request to communicate with external systems, such as fetching data from an API or sending information to a third-party service. These logs capture the full details of the HTTP requests and responses, providing useful insights for diagnosing problems related to external connections.
In HTTP logs you can view the log id, connector name,received time,http status,details(See the below picture)
HTTP Status: The status code returned by the HTTP request (e.g., 200 for success, 404 for not found, 500 for server error).
Details:-
View Log Details: Clicking this opens a pop-up where you can view more specific details about the HTTP request.When you click View Log Details, you can see two key pieces of information(See the below picture)
HTTP Response Tree: A structured view of the data received from the external system (API response). This tree helps you navigate through the response data to identify any issues or unexpected values.
Log Information: A summary of the HTTP request, including the request URL, headers, response status, and any error messages if the request failed.
Filter Logs
You can customize the logs list by filtering based on the connector name, date range, or both. To filter by connector name, select the specific connector you wish to review from the dropdown menu. If you want to narrow down the logs by a specific time period, choose the desired start and end dates in the date range fields. You can apply both filters simultaneously to refine your search further. Once you have made your selections, click on "Apply Filter" to update the logs list accordingly. This functionality allows you to quickly find relevant logs, making it easier to monitor and troubleshoot your workflows.
(See the below picture)
With the search option, you can locate logs based on the connector name, connector ID, or received time.
By clicking on the Export Logs option, you can export all connector information from the current logs page into a CSV or XLS file.(See the below picture)
Last updated