Share this page

# Service Level Agreement wizard

The Service Level Agreement - Goal Dentition wizard guides you through the steps of defining thresholds and goals. The pages included in the wizard and their order depend on the measurement that is selected. This wizard enables you to define goals or service level agreements (SLAs) for your load test scenario.

To open the wizard:

- From Analysis: Tools menu > Configure SLA Rules > Service Level Agreement window > New button

- From Controller: Design tab > Service Level Agreement window > New button

In this topic:

## Select a Measurement for Your Goal page

The Select a Measurement page enables you to select a measurement for your goal. You can only select one measurement for each SLA. The wizard pages that follow are determined by the measurement that you selected.

Measurement type | Description
--- | ---
SLA status determined over the whole run | Evaluates a single SLA status for the whole scenario run. Select one of the following measurements: Transaction Response Time (Percentile) Total Hits (Status per run) Average Hits per second (Stauts per run) Total Throughput (bytes) (Stauts per run) Average Throughput (bytes/second) (Stauts per run) Passed Transactions Ratio
SLA status determined per time intervals over a timeline | Evaluates SLA statuses at set time intervals within the run. Select one of the following measurements: Transaction Response Time (Average) Errors per Second (Stauts per time interval) The time intervals at which the SLA statuses are evaluated are known as the tracking period. For details, see Tracking period.
SLA status determined by APDEX | Evaluates an APDEX measurement for the whole scenario run. Select Transaction Response Time (APDEX)

Back to top

## Select Transactions page

This wizard page enables you to select transactions to evaluate as part of your goal.

This page is displayed when creating an SLA for Transaction Response Time by Average, Percentile, or APDEX. To define this SLA, at least one of the Vuser scripts participating in the scenario must include a transaction.

The Select Transactions page contains two panes:

.Available Transactions: Lists the transactions in the Vuser scripts participating in the scenario.

Selected Transactions: Lists the transactions in the Vuser scripts participating in the scenario that have been selected for the SLA.

Use the buttons to perform the desired actions:

Action | Description
--- | ---
Add selected transactions | Add the selected transactions from the Available Transactions list to the Selected Transactions list.
Remove selected transactions | Remove the selected transactions from the Selected Transactions list.
Add dynamic transaction | Add a transaction that is not currently in the script but will be generated dynamically at runtime. When the script is run and the specified transaction is generated, it is automatically found and added to the SLA.
Remove dynamic transaction | Remove the selected dynamic transaction.

Back to top

## Set Load Criteria page

This wizard page enables you to select load criteria to take into account when testing your goal. The page is only displayed when defining an SLA that determines SLA statuses per time interval over a timeline.

The measurement you selected for the goal is shown in a read-only field at the top of the page.

Tip: In the next wizard step (Set Threshold Values page), you set different thresholds for each of the load ranges that you select here.

User interface elements are described below:

Field | Description
--- | ---
Load Criteria | The load criteria that you want to use. For example, if you want to see the impact of running Vusers on the measurement, select Running Vusers. To define an SLA without load criteria, select None.
Load Values | Valid load value ranges are consecutive—there are no gaps in the range—and span all values from zero to infinity. Less than. Enter the upper value for the lower range of values for the load criteria. The lower range is between 0 and the value you entered. It does not include the upper value. For example, if you enter 5, the lower range of values for the load criteria is between 0 and 5, but does not include 5. Between. The in-between range of values for the load criteria. Enter lower and upper values for this range. The lower range is included in this range; it does not include the upper value. For example, if you enter 5 and 10, the in-between range of values for the load criteria is from 5 and up to, but not including, 10. Note: You can set up to three in-between ranges. Greater than. Enter the lower value for the upper range of values for the load criteria. The upper range includes values from the value you entered and on. For example, if you enter 10, the upper range of values for the load criteria is from 10 and on.

Back to top

## Set Threshold Values page

The Set Threshold Values page enables you to set thresholds for the measurements you are evaluating in your goal.

The Set Threshold Values page contents depend on the values you chose in the earlier pages.

- Set Percentile Threshold Values page
- Set Threshold Values page - APDEX
- Set Threshold Values page - goal per time interval
- Set Threshold Values page - goal per whole run

Set Percentile Threshold Values page

This page enables you to define the percentage and thresholds for the measurements you are evaluating in your goal. The measurement you selected for the goal is shown in a read-only field at the top of the page.

The Percentile SLA enables you to measure whether the percentage of transaction samples meets the defined threshold criteria.

Field | Description
--- | ---
Percentile | Percentage of transactions to measure against the configured threshold.
Provide threshold value for all transactions | To apply one set of threshold values to all transactions selected for the goal, enter the threshold value and click Apply to all. These values are applied to all the transactions in the Thresholds table at the bottom of the page.
Transaction name | The transaction from the scenario run.
Threshold | The threshold value for the selected transaction. You can enter a threshold value to 3 decimal places.

Set Threshold Values page - APDEX

This wizard page is shown when you chose Transaction Response Time > APDEX as a measurement. It enables you to set threshold values for satisfactory response time and tolerable response time, for each transaction.

The Thresholds table shows the thresholds for your APDEX rating. To define different thresholds for each transaction, enter the required Satisfied and Tolerating thresholds.

The satisfied threshold must be less than the tolerating threshold.

To apply one set of threshold values to all transactions selected for the goal, enter the threshold values in this table and click Apply to all transactions. These values are applied to all the transactions in the Thresholds table.

Set Threshold Values page - goal per time interval

The Thresholds table shows the thresholds for your goal. If you defined load criteria, enter thresholds for each range of values.

Note: If the maximum threshold value is exceeded during a particular time interval during the run, Analysis displays an SLA status of Failed for that time interval.

If you defined load criteria in the Set Load Criteria page, you must set thresholds per each of the defined load ranges. If you did not define load criteria, you set one threshold value. For Average Transaction Response Time, you set threshold values for each transaction.

Tip: To apply one set of threshold values to all transactions selected for the goal, enter the threshold values in this table and click Apply to all transactions. These values are applied to all the transactions in the Thresholds table at the top of the page.

Note: Threshold values for selected transactions do not have to be the same. You can assign different values for each transaction.

Set Threshold Values page - goal per whole run

This wizard page enables you to set minimum thresholds for the measurements you are evaluating in your goal.

The Threshold field indicates the minimum threshold value for the selected measurement.

For the Passed Transactions Ratio measurement, select the minimum percentage (between 0-100) of passed transactions.

Note: If the value of the measurement is lower than this threshold during the run, Analysis displays an SLA status of Failed for the entire run.

Note: You can enter a threshold value to 3 decimal places.

Back to top

See also:

- Service level agreements overview
- Define service level agreements

https://admhelp.microfocus.com Professional Performance Engineering,VuGen 8942
Tips to improve your search results... OpenText™ Professional Performance Engineering Help Center OpenText™ Professional Performance Engineering Help 25.1-25.3 All View Local Help Center View Online Help Center Version: