How Performance OLA Reporting Works

Managing Application Performance OLAs › How Performance OLAs Work › How Performance OLA Reporting Works

How Performance OLA Reporting Works

A performance OLA shows how well a user-defined application is performing by counting, on an hourly basis, the percentage of IPv4-based transactions that are faster than a given threshold. An example of a performance OLA would be that 90 percent of server response times must be under 20 milliseconds. The result of a performance OLA is displayed in a report which indicates, on an hourly basis, whether the application meets the operational level agreement.

The management console measures hourly operational level compliance based on the threshold you specify. You can specify a threshold with resolution of up to 3 decimal places, such as 93.999. It can take up to an hour to report an OLA compliance violation.

The management console does not collect OLA data in the same manner as 5-minute data. For performance OLAs, the monitoring device:

Compares every transaction to see whether it meets the OLA thresholds.
Records how many transactions pass and fail every hour.

An analogy would be, instead of recording the average speed of cars on an interstate every five minutes, the management console marks whether each is traveling above 40mph and reports the successes and failures each hour.

By comparison, the management console uses thresholds to monitor application performance based on the average response time of a particular metric during a 5-minute interval.