This page eases the troubleshooting if you face any issue with any of the integrations in your ZigiOps instance.
You should follow a few simple steps to drill down to the data itself.
- Access the ZigiOps web console.
- Go to Troubleshooting > Integration > Operation page.
- Select the desired Action Run and click on the desired phase tab to review the available details.
An action run is the complete workflow of an operation. Each action run goes through 4 phases.
Note that the HTTP phases are disabled by default, and you could enable them from the General Settings page.
Phase 1 - Extract HTTP
The initial phase of the action run, in which you can see the HTTP response, is returned by the queried system. Extract HTTP data contain the request ZigiOps sends to the Source System and the target system's response (the data).
Phase 2 - Extract
The second phase of the action run, in which you will see the data extracted from the HTTP response, returned by the queried system. Extract Data contain the data extracted from the source system as is configured in the Configurator.
Phase 3 - Load
The third phase of the action run, in which you will see the data that ZigiOps will load to the target system.
Load Data is the transformed data that ZigiOps will report to the target system. In the Load, we can see the Configurator mappings applied.
Phase 4 - Load HTTP
The last phase of the action run, in which you will see the data loaded to the target system. Load HTTP data contains the request ZigiOps sends to the Target System (the transformed data) and the Target System's response.
The Status tab contains information for the phase execution flow. For example, if the action run was executed successfully or not.