Integration performance enables you to see beyond just the status of an integration, and provides visibility of all events taking place inside the integration. Using this, you get the means to debug integrations, check the tasks being consumed by a user or an integration, or see if every step of the template is performing as intended.
To open an integration’s performance, go to the Templates tab in your dashboard and hover over the stats of any template. You will be able to see the “Integration View” tooltip as shown below.
If no integrations have been created against a template, you will see “No integrations to see” tooltip on hover, and the stats will not be clickable.
End users page
Once you click the template stats, you will be taken to the end user information for that template as shown below. This will show you all your users who have made an integration using this template. This is ordered by the most recent users first.
On the top left, you will be able to see the template name, ID, and the stats. In the middle, you’ll see the users and their registered details. If your SDK is set up to receive the username and profile image, then these will appear here. Here is how you can set these up. If these details are not provided, you’ll just see the user IDs. You can also copy a user ID by hovering over it and clicking it.
For each user, you’ll see their number of total integrations, the number of total tasks consumed, and the status of the user. A user can have different statuses based on their integrations.
Here are all possible statuses that a user can have:
a) Active: The user has at least one active integration.
b) Inactive: The user has no active integrations.
c) Paused: The user has reached their task limit.
d) Auth Missing - The user’s authentication for an integration is not found or has been deleted.
e) Creation Failed - An integration creation process for this user has failed and the setup was unsuccessful.
These above statuses related to integrations can be seen in more detail here.
You can click on any user from the list to see all the integrations they have created.
This will again be ordered by the recency of integrations. For each integration here, you’ll be able to see its name and ID, the tasks consumed by it, the status of the integration (active, inactive, paused), and the number of runs completed by it. One complete operation or a flow in a template is defined as one run. More details on it can be found here.
Integration detail page
You can click on any integration for a selected user to see that integration’s details. In the example provided above, let’s say that you clicked on the “Mailchimp sync” integration. This will now take you to the integration details page which will look like this:
This page will have all the recent runs that have taken place in the integration. The name of the run is the name of the first step for that run in the template. Mostly, it is a trigger step that starts a run or an operation. A run can also be started with a Setup step, as in the case of using queries to import records.
For every run, you’ll be able to see these details:
1. The time when the run occurred. You’ll be shown how long ago the run occurred. Hovering over this info will show you the exact time of occurrence as shown below.
2. The number of tasks consumed by the run.
3. The duration taken for the run to complete.
4. The link to this run in the integration logs. This will only be shown to the staff account members that have the authority to debug integrations. More information on staff accounts is provided at the end of this section.
5. The status or the HTTP response of the run. This will show a green 200 status if everything in the run was successful. Otherwise, it will show a red error code for the first failed task in the run. Hovering over this status will also show the error code description. In our running example, the first run has a failed task due to which it shows us a service unavailable error code as shown below.
Staff accounts: We have a permission system in place where we mark user accounts as "staff". If you are staff, you’ll be able to see some additional details that are helpful in debugging integration issues, such as the links to integration logs.
You can also click the View More button at the bottom to see the details of older runs that have occurred.
You can also click on any run on the integration detail page to see the details of all the tasks inside that run. The run will expand and you’ll be able to see all the template steps inside it with the exact hierarchy. Expanding the first run in our current example will look like this:
Similar to the run details, you’ll be able to see the analytics for each task inside the run. These will be: occurrence time, tasks consumed, duration for the step to complete, link to the logs, and the HTTP response code.
The tasks that have failed in this run will be colored red. It can be seen that in the current example, the conditional step at the end of the loop has failed to execute due to a 503 (service unavailable) error status. This is the reason that the overall run is showing the same error status.
If a loop is being performed in the run, it will be shown with all its steps for each iteration. The iteration number is written with each loop step, as shown in the above example. To see the steps inside the second loop iteration, you’ll need to click on the View More button.
On the top, you are provided three different dropdowns to filter your run data. This is shown below.
With the first filter, you can show or hide internal steps in your run data. Internal steps are tasks that are performed on the back-end by Integry, and are not added as steps in the template builder.
By default, the internal steps are hidden from your run details. But you can use the above filter to view the internal steps as well. In our current example, viewing internal steps will look like this:
The implicit steps can now be seen inside the loop, like using the “Get” action from the Mailchimp app, as well as the steps to fetch data from the data store.
You can use the second filter to show all runs (the current case) or just the failed runs in the integration.
With the third filter, you can choose to see the runs in the last hour, last 24 hours, or the last 7 days.
You can click on any task inside a run to see its details. This will show you all the input and output data for that task. For our current example, clicking on the Mailchimp Create Contact action will open the details as shown below.
You can select from all the possible data types that can be found in an activity and its endpoint. This includes all inputs and transformations (request bodies), raw responses (response body), formatted responses (object output), and headers. In our current example, we can see the Request Body template in Twig format that was set for this Create Contact action’s endpoint in the Mailchimp app.
You can see the inputs and outputs of other steps in a similar manner as shown above.
Learn how to see the insights and reports for your integrations.