ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

IIB monitoring Elapsed Time Average


Article ID: 213385


Updated On:


CA Application Performance Management (APM / Wily / Introscope)


The metric Elapsed Time Average metric does not show the correct value of the average from the minimum and maximum as below:




 Elapsed Time Average is not the average of Elapsed Time Maximum and Elapsed Time Minimum.


CA Application Performance Management 10.7 agent release.

IIB monitoring.


Below how the Elapsed Time Average is measured:

MBConstants.ELAPSED_TIME_AVERAGE, elapsedTimeTotal / messageflowInvocationTotal

Elapsed Time Average = Elapsed Time Total / (message flow invocation total) 
message flow invocation total   = commitCount + backoutCount;

So Elapsed Time Average is NOT an average of Max and Min. Also, there is NO metric as Average for Elapsed Time Maximum and Elapsed Time Minimum.

As a workaround, you can create a calculator from Elapsed Time Maximum and Elapsed Time Minimum. Please refer to the below documentation to accomplish it: