Administration › Administration Page Reference › Policies - Performance OLA Thresholds

Policies - Performance OLA Thresholds

Add or edit operational level agreement thresholds (OLA thresholds) to measure compliance on client networks. You can set OLAs for networks that are assigned to a particular network type, and set a default OLA for networks that do not have an assigned network type.

Frequently Asked Questions

• How is OLA data tracked and then stored? Unlike performance data, the management console does not create 5-minute averages of OLA data. On an OLA metric, the management console evaluates each transaction for OLA compliance, computes the hourly percentage of transactions that met compliance, and stores those hourly percentages for up to 25 months without ever rolling them up. There can be up to an hour lag before an OLA shows as violated. An incident lag will be 5 minutes or less.
• Why should I add performance OLA thresholds? If you have assigned network types to your networks, the management console can monitor compliance with performance OLAs across each network type using appropriate performance OLA thresholds, and provide more accurate reporting. Unlike performance thresholds which indicate when application performance across a network is Normal, Minor (yellow), or Major (orange), a performance OLA calculates whether the application performance meets the required operational level. Remember, a performance management threshold tells you whether an application is performing normally, and a performance OLA tell you whether the application is performing within acceptable boundaries. In most cases, you do not want to know that an application is performing normally to find that its performance is unacceptable.
• Why use 2 OLAs? Set up internal versus external OLA agreements, or can establish 2 tiers of compliance.
• How do I set performance OLA thresholds for an application across a group of remote networks? If you have assigned network types to your networks, the management console can monitor compliance with performance OLAs across each network type using appropriate performance OLA thresholds, and provide more accurate reporting. For example, you can set a static threshold for Server Response Time on networks that have similar latency characteristics.
• If I did not implement network types, can I adjust the performance OLA thresholds for the application? Yes, but before you do, make sure you understand how performance OLAs work.

Property Details

Complete the following fields:

Threshold Levels

Specifies up to 2 operational levels for each OLA metric. Use different operational levels to measure compliance, for example, with internal and external OLAs.

For each operational level, specify a threshold for the minimum percentage of observations during the 1-hour reporting interval that must meet the OLA metric’s threshold value. You can specify a threshold value up to 3 decimal places, such as 93.999. When you finish, click OK.

Threshold Values

Specifies how the threshold values for the operational level are specified. If you are editing the Default application OLA, these options are not applicable:

• Default. The management console dynamically updates the threshold value based on changes to the application’s Default OLA.
• Customize. Lets you override the dynamic default value and specify the thresholds for observations and OLA metric value you want.

Include this network type in OLA

Specifies whether to include the response time metric in the OLA. To select this option, the Customize option must be selected.

N % of observations must be less than N milliseconds

Specifies a threshold for the minimum percentage of observations during the 1-hour reporting interval that must meet the OLA metric’s threshold value. You can specify a threshold value up to 3 decimal places, such as 93.999. To edit the threshold, the Include this network type in OLA option must be selected.

More information:

How Performance OLAs Work