Managing Application Performance OLAs › How Performance OLAs Work › Performance OLA Tips and Tricks

Performance OLA Tips and Tricks

We recommend creating an application performance OLA for user-defined applications that represent the largest (or most constant) amount of traffic to each site to get more observations and statistical significance. You cannot set operational levels for system-defined applications.

When setting up a performance OLA:

• Separate data center metrics from network metrics. Not every metric is meaningful for every network. For example, on back-end applications, you might not want to see Network Round Trip time tracking.
• It is appropriate to use longer timelines when deciding OLA threshold values to eliminate transient spikes or dips. You can also exclude a particular metric from the OLA.
• Define up to two thresholds to measure application compliance with an operational level, for example, to set internal and external operational levels. In general, define an operational level at 90 percent or higher so that the management console can offer additional insight into the variability of performance. Alternatively, you are not required to set performance threshold levels for an OLA metric.

With the correct value for each threshold level, the management console will have historical trend data on the 5-minute averages and on the worst performing (highest percentile) transactions that the users in each remote location are experiencing.

More information:

Edit an Application Performance OLA