In this video we will show you Alumio's integration dashboard
Alumio offers you a dashboard which gives you an insight in the status of your integration environment. The integration dashboard serves as the main point of entry for any integration environment set up in Alumio.
At the top of the page we see the health monitoring section. This section gives the user an indication of the general health of the integration environment.
The first block states the health of the disk space. An exclamation mark will be shown if the system does not have disk space available, to perform the required operations.
The second a third block indicate if there have been any errors while respectively retrieving or publishing data from or to external systems. In this case we can see that both cases have got an error recently. Clicking on the red exclamation mark gives us more information regarding what has gone wrong. In this case we can see the threshold of 100 failing exports has been reached.
The fourth and fifth block gives the user more information regarding the status of the tasks flowing through the system.
Before we continue we go to the next section of the dashboard, a quick introduction to our terminology is required. Within Alumio we setup routes in order to transfer data between systems. A route is responsible for one thing: Transferring a data entity from system A to B.
To make it more clear, an example is required. An example of such a route would be: Route order from eCommerce platform (such as Magento) to ERP (such as SAP).
In this example our data entity is an order. The source of the order is your eCommerce platform and the destination is your ERP. The sole purpose of this route is to make sure that any order placed in your eCommerce platform is transferred to your ERP.
With this knowledge, we can continue to the next section of the dashboard: the real time statistics. This section is divided into three important metrics:
- New tasks
This shows the amount of tasks or data transactions sitting in a queue. Most integrations are asynchronous, meaning that the data transactions are executed at a later point of time. When data is retrieved from a source system, it is added to the queue for the given route.
- Currently processing
This shows the amount of tasks or data transactions that are currently processing to be send out to the destination system.
- Stuck tasks
This shows the amount of tasks that are stuck in the system. An example when this would happen, is when a destination system responds with a time out.
In the right upper corner we are able to filter out to the specific route. Which would update the metrics to only show the data for the selected routes.
The section below shows the user historical data. Again, three important metrics are shown:
- Total tasks
The first metric shows the total amount of tasks or data transactions created in the integration environment is.
- Finished tasks
Secondly, the amount of finished tasks or successful data transactions.
- Failed tasks
And the last metric is the amount of failed tasks or failed data transactions within the integration environment.
Applying a Timeframe filter will give you the results based on the selection you have chosen.
Changing the aforementioned filter will update these metrics with the data of the given route.
The last section of the dashboard shows the task flow for the selected configuration. Any failed tasks or data transactions will cause a bar to appear on this graph. This is for spotting anomalies in failed tasks or data transactions for a given route.
As we can see, there is an anomaly in the last hour as we had four failed tasks or four failed data transactions. Based on this, a user can start to diagnose what has gone within their integration environment.
You now have a good sense of how the dashboard of Alumio works.