HP WebQoS Software manual Policies Set in WebQoS, Service Level Objectives for Site

Policy and Rule Descriptions

Policies Set in WebQoS

Policies Set in WebQoS

There are two types of policies for WebQoS: business-oriented SLOs and operations-oriented Threshold Policies. You define these two types of policies and prioritize them relative to one another. WebQoS trades off meeting these policies based on their priorities.

WebQoS uses priorities to determine which corrective actions to take when one or more of the SLOs or Threshold policies are violated. When multiple policies are violated, WebQoS executes the corrective actions configured for the highest priority policy.

The scope of priorities apply across both SLOs and thresholds.

SLOs and thresholds involving the CPU are system-wide. All other SLOs and thresholds are site-specific.

Service Level Objectives for Site

Service level objectives (SLOs) are measures that are typically negotiated with a customer or business unit and specify the level of service they expect you to provide. WebQoS helps you to meet these expectations by monitoring compliance and taking corrective actions. SLOs put limits on response time delays and minimum concurrent session capacity.

The SLOs supported by WebQoS are:

•Maintain less than NUMBER millisecond avg response time for CLASS priority requests

You can choose an appropriate NUMBER to input for the average response time (in milliseconds) for each request classification (High, Medium or Low) supported by the site.

•Support at least NUMBER WebQoS sessions

This SLO lets you support a specific NUMBER (for example, 20) of concurrent sessions. It is tied to the average response time SLO described in the previous bullet. It can only be violated if one or more SLOs or thresholds are violated. The request classification CLASS information is not supported.

Concurrent sessions means the total number of sessions that have not

122 Appendix A