In a previous post, we have seen how you can make use of the new feature of IIB v9.0 to enable the collection of statistics for flows, applications or servers and how you can use the Web UI to compare the performance of flows by selecting a resource and looking at the live performance data for flows. Once you have seen how the flows are doing relative to each other, you might want to focus on a particular flow and analyze its performance. This is where the Flow Analysis comes into its own.

You can open this view in one of the two ways:

  1. you can expand the integration server, application, library or service until you find the flow you want it, select it in the tree and then, on the right hand side, select the tab called “Statistics”
  2. In the Flow Comparison view, you can click on the magnifying glass. This will open a new browser tab

imageTip: If you need to analyze the performance of a specific flow repeatedly, you might want to bookmark its Statistics tab, with an URL of the form:

                  http://localhost:4414/#messageFlow/1/executiongroups/default/applications/My application/messageflows/My flow1

Once in a Flow Analysis view, you see three sections

  1. The charts show a graphical visualization of three metrics for your flows. You can change the metrics or the time range. The graphs are redrawn as new data comes in.
  2. The node table contains the statistics for the nodes in the flow for key performance metrics for each node, CPU time and Elpased time.
  3. The flow profile diagram gives you a quick view of the shape of the flow, in-lined  in the web tool, . You don’t have to switch to Integration Toolkit to see how the nodes in the flow are wired together.

The charts and the tables are updated every twenty seconds with a new set of performance figures.  The title of the charts section shows the time when the last update took place. The flow profile diagram is static.

In the next section, we’ll look into this view in more detail.

Join The Discussion

Your email address will not be published. Required fields are marked *