Service policy settings

You can change existing service policies or transaction classes, which together create an operational policy.

To view this administrative console page, click Operational Policies > Service policies > service_policy.

To create, modify, or remove service policies and transaction classes, you must have administrator or configurator administrative privileges.

Name

The name of the service policy is a user-defined field that must contain alpha or numeric characters. Use consistent and meaningful service policy names, for example, PLATINUM, GOLD, SILVER, and BRONZE.

Description

The description field complements the name field and is user-defined. This field is optional, but in environments with multiple system administrators, you must complete this field with useful information. For example, a description field for a PLATINUM policy might read, The PLATINUM service policy is reserved for the highest priority work.

Goal type

This is a selectable field that can be one of four values:

Average response time: Indicates high priority work. This field is used with the goal value and importance to limit the time this work is kept in queue.
Percentile response time: This a percentage of requests handled in a specific period of time. This field is used with the goal percent to define the percentage of requests per seconds or milliseconds.
Discretionary: the default value for goal type. Discretionary indicates work that is not high priority and can be scheduled by the on demand router based on the existing workload in the queue.
Importance When the system is under stress, the importance value determines the application work that can best tolerate performance decrements. The higher the importance, the less tolerant that the work associated with that service policy is to performance reductions. For the PLATINUM example: select Highest as the importance. Do not set all policies to the highest level of importance, unless all policies can degrade to the same proportion when the system is overloaded.

Note: If the cell custom property disableResponseTimeGoals=true, a goal type of importance will display for service policy goal types. This goal type is utilized to establish that only the importance aspect of the service policy will be used.

Goal value

Set this value to equal the maximum time allotted for completion. For example, PLATINUM work should not exceed two seconds. The goal value field is unavailable when the goal type is discretionary.

If you are using a response time goal for Session Initiation Protocol (SIP) traffic, then the goal value must be under 500 ms.

Goal percentile

Specifies the percentage of requests to be handled in a specific time frame. The goal percentile value can be a whole number from 1 to 99 inclusive. This field is available when the goal type is percentile response time.

Importance

Indicates a level of importance. The importance value is unavailable when the goal type is discretionary.

Monitor for persistent policy violations

Requires different settings depending on the type of service policy goal type:

Average response time view
- Goal Value: An integer that indicates the milliseconds, seconds or minutes of the goal value. Acceptable values are 0 to 300000 milliseconds, 0 to 300 seconds, and 0 to 2147483647 minutes.
- Time Period Value: An integer that indicates the milliseconds, seconds or minutes after which the goal value is in violation. This value can be 0 to 1 day, inclusive.
Percentile response time view
- Goal Percentile: An integer that indicates the percentage of requests under the goal value for which to monitor. This value can be 0 to 100, inclusive.
- Time Period Value: An integer that indicates the milliseconds, seconds or minutes at which the goal value is in violation. This value can be 0 to 1 day, inclusive.

Membership

Specifies an association between transaction classes and a respective service policy. Each transaction policy can be contained in only one service policy. You can perform the following actions:

New: Creates new transaction classes, which can then be made members of a new or existing service policy.
Remove: By selecting a transaction policy from the membership field and clicking Remove, you can remove the association between a transaction policy and a service policy. This action deletes the transaction policy altogether.
Modify: Changes an existing transaction policy. To edit a transaction policy, you must first select the transaction policy you want to edit and click Modify.
Move: Moves transaction classes from one service policy to another. Because a transaction class cannot exist outside of a service policy association, the only other option to move is remove if you no longer want a transaction class and a service policy to be affiliated. To move a transaction class, select the policy you want to associate with another service policy and click Move.