If you need to troubleshoot your flows in IBMÂ® App Connect on IBM Cloud, or find out what they’re doing, you can use the Kibana logs in the IBM Cloud Log Analysis service.
App Connect flows emit the following types of log entry:
An error message is emitted when a trigger, action, or some flow logic has failed.
This error type is enabled by default and is logged to the built-in viewer thatâ€™s available on the flow tile on the App Connect dashboard, and to the Kibana logs.
An information message is emitted at key points, such as when a flow is triggered, or when it completes successfully.
This error type is enabled by default and is logged to the Kibana logs only.
A debug message logs detailed information about the execution of flows, including payload data.
You must enable this error type manually, and itâ€™s logged to the Kibana logs only. These log entries are visible to IBM operators.
This guide shows you how to enable debug logging and view the logs.
Before you start:
- You need to have created an instance of IBM App Connect in IBM Cloud (Bluemix).
- These instructions assume that youâ€™ve created at least one flow.
Debug your flows:
- If an error message is emitted when a trigger, action, or some flow logic has failed in your flow, the quickest way to find more information about that error is to click the error icon on the flow tile on the App Connect dashboard.
- To record debugging information for a flow in the Kibana logs, open the tile menu and select Enable debug logging. (This menu item is only visible when using App Connect in IBM Cloud.)
- Click Enable on next restart.
- If your flow is already running, stop and restart it. Debug logging is now enabled for that flow.
- To view error, information, and debug messages for your flow, open the App Connect hamburger menu , expand Manage, and select Logs.
- When debug logging is enabled, youâ€™ll see a log entry for each step in the flow that completes successfully. The log entry includes the output data from that step (in JSON format). Each step in the flow has access to the output from all previous steps.
For an example of how to use the debug entries from each step to diagnose a failure in the flow, see the blog post Debugging flows in IBM App Connect.
For more information about how to use Kibana logs, see the Kibana user guide.