Policy and Rule Descriptions
Policies Set in WebQoS
expired (based on the configuration of the advanced features discussed in “Session Timeouts” on page 69) and are possibly active. This number does not indicate the total number of sessions currently active on the system.
•Support at most NUMBER WebQoS sessions
This SLO lets you support a specific NUMBER (for example, 1000) of concurrent sessions. The request classification CLASS information is not supported.
Concurrent sessions means the total number of sessions that have not expired (based on the configuration of the advanced features discussed in “Session Timeouts” on page 69) and are possibly active. This number does not indicate the total number of sessions currently active on the system.
Service Level Objectives for the Service
WebQoS offers the following SLOs at the service level:
•Support at most NUMBER WebQoS sessions
This SLO lets you support a specific NUMBER (for example, 1000) of concurrent sessions. The request classification CLASS information is not supported.
Concurrent sessions means the total number of sessions that have not expired and are possibly active.
•Ensure less than NUMBER millisecond response time for CLASS requests to URL GROUP
For requests to the specified URL(s), make sure the response time is met for the specified request classification. Refer to the online help for information about using wildcards in the URL(s).
•Ensure MEASUREMENT is CONDITION NUMBER
Make sure the specified measurement meets the specified condition.
Appendix A | 123 |
