Monitoring
In any integration, the most important thing, besides the integration working, of course, is being able to monitor it and be notified in case of errors. We created several resources to abstract this in the simplest way possible for developers and end-users.
To access monitoring, enter in the Automations > Monitoring menu
On the screen, there are several possible filters to be used to find the desired execution, such as:
Processing status
Package
Automation
Start and end date and time of execution
When you find the desired execution, to view the details, click on Details in the “Actions” column.
The header displays general information, such as unique run ID, start and end time, and total processing time. In addition, it has the total of processed records and errors sum.
In the central part, we have two tabs: Processing logs and Traces.
Processing logs
In this section, we have the main log returned by the tool with all processed records and error messages. The log will be based on the metadata definition and the data extraction return.
All fields are filterable through the fields at the top of the table. To see all available fields is necessary to click on Expand. If there are many records, you may need to download the records in CSV to analyze them in tools such as Excel or Google Sheets. If the result has more than 10,000 lines, a new background task will be started and, when finished, will be available in the top menu, in the alerts icon.
Traces
In this section are the more technical logs representing the output of the console.log commands executed during the integration. By default, flows have automatic logs that measure the time of each step and the total execution time. The rest is up to the integration developer.
Last updated
