How to troubleshoot or debug integrations

This article describes the capabilities for troubleshooting and debugging distributed integrations

The platform delivers end to end logging capabilities. From within the platform, insights to troubleshoot or debug integrations can be gained by viewing log information at the incoming configuration on task level and from within the notification center.

General configurations
A user may configure the level of logging by choosing thee different Log requests while setting up a Client. The options are Full, Long and Simple. There’s an additional setting which gives the user ‘Verbose output’ during development.

Incoming logs
Within the incoming logs, a user is able to view the ID of the incoming run, when it has been executed and when it has been finished. It shows the number of created finished, skipped and failed tasks.

Task logs
At task level, a user can display the end result of the data entity after transformations, the Import and Export messages. These logs contain actions that are performed during the fetching of data from a source and actions performed during the publish action to an endpoint.

The extend of the logging information on Import and Export messages depends on the Log request setting that a user has configured, and/or the Verbose output selection. The logging includes system messages from third party systems and a detailed timeline process of the messages that go back and forth between Alumio and third party systems.

Elastic Stack
Certified Alumio engineers and integrators gain access to the Elastic Kibana instance of a customer. This gives them even more detailed logging information regarding integrations, which can be used for debugging and troubleshooting purposes.