You can configure your integration servers to collect statistics about the operation and behavior of your message flows. Use this information to assess the performance of your message flows.
Read the concept topic Message flow statistics and accounting data
Measures of performance typically include product speed in terms of processing rate and response times, and resource usage in terms of the CPU and memory consumed. In order to assess the performance of an application, metrics are used to compare the actual performance with the required or expected performance, using measures such as the number of messages per second, elapsed time, CPU utilization, or CPU cost per message. You can use the message flow statistics and accounting data to assess the performance of your message flows and applications using some of these metrics, and to identify the message flows and nodes that might benefit from tuning to improve performance.
Message flow statistics for subflows are accumulated in the metrics for the top-level parent flow. For example, if a subflow contains an Input node, the number of message flow threads and any node-level additional instances from the subflow will be reported in the NumberOfThreadsInPool property of the statistics for the parent flow.
You can start or stop the collection of statistics data by modifying the server.conf.yaml configuration file for the integration server. For more information, see Starting and stopping the collection of message flow statistics and accounting data.
You can view the collected statistics by using the web user interface; see Viewing message flow statistics and accounting data. You can also configure your integration servers to report the statistics and accounting data to IBM Cloud Log Analysis, where you can view them in a Kibana dashboard. For more information, see Reporting logging and statistics data to IBM Cloud Log Analysis and displaying it in a Kibana dashboard.