You will define an SLA in Analysis after the scenario run.
Note: The preferred place to define an SLA is before a scenario run in the Controller. However, for the purposes of this tutorial, because you are not analyzing the same test scenario that you ran in previous lessons, you will define the SLA in Analysis. To define an SLA in the Controller, click New in
the Service Level Agreement section of the Design tab.
You will now define an SLA that will set specific goals for the average transaction response times for the book_flight and search_flight transactions in the sample session file.The average transaction response times will be measured at set time intervals within the run.
Note: The preferred place to define an SLA is before a scenario run in the Controller. However, for the purposes of this tutorial, because you are not analyzing the same test scenario that you ran in previous lessons, you will define the SLA in Analysis. To define an SLA in the Controller, click New in
the Service Level Agreement section of the Design tab.
You will now define an SLA that will set specific goals for the average transaction response times for the book_flight and search_flight transactions in the sample session file.The average transaction response times will be measured at set time intervals within the run.
To define an SLA:
1 Open the SLA Configuration Wizard. Select Tools > Configure SLA Rules. The Service Level Agreement dialog box opens. Click New to open the wizard.
1.Select a measurement for your goal.
Note: The first time you open the Service Level Agreement wizard, the Welcome page is displayed. If you do not want this page to be displayed the next time you run the wizard, select Skip this page next time.
In the Select a Measurement for Your Goal page, select Transaction Response.Time average click Next
In the Select a Measurement for Your Goal page, select Transaction Response.Time average click Next
2 Select transactions to monitor.
In the Select Transactions page, you select the transactions you would like to monitor from the Available Transactions list, which is a list of all the transactions in the script. Double-click the book_flight and search_flight transactions to select them. Click Next
3 Set the load criteria.
In the Set Load Criteria page, you instruct the SLA to take different load scenarios into account.
Select Running Vusers from the Load Criteria drop down list and set the Load Values to look like the following example:
You just set the SLA to determine an acceptable average transaction response time over three potential load scenarios:
➤ Light load. Between 0 and 19 Vusers
➤ Average load. Between 20 and 49 Vusers
➤ Heavy load. More than 50 Vusers
4 Set threshold values.
In the Set Threshold Values page, you define the acceptable average transaction response times for the book_flight and search_flight
transactions.
Set the threshold values to look like the following example:You just determined that for both selected transactions, the following average transaction response times are acceptable:
➤ Light load. 5 seconds or less
➤ Average load. 10 seconds or less
➤ Heavy load. 15 seconds or less
Note: Threshold values for selected transactions do not have to be the same.You can assign different values for each transaction.
Set the threshold values to look like the following example:You just determined that for both selected transactions, the following average transaction response times are acceptable:
➤ Light load. 5 seconds or less
➤ Average load. 10 seconds or less
➤ Heavy load. 15 seconds or less
Note: Threshold values for selected transactions do not have to be the same.You can assign different values for each transaction.
5 Save the SLA.
To save the SLA and close the wizard, click Next then Finish then Close on the pages that follow.
Analysis applies your SLA settings to the default Summary Report. The report is then updated to include all the relevant SLA information.
1 comment:
Found this very helpful. Thank you
Post a Comment