Merge pull request #259468 from ntrogh/alt-content-freshness-1123

[Azure Load Testing] Content freshness November 2023

Author: v-regandowner

articles/load-testing/concept-load-testing-concepts.md

@@ -6,13 +6,13 @@ ms.service: load-testing
 author: ntrogh
 ms.author: nicktrog
 ms.topic: conceptual
-ms.date: 11/03/2022
+ms.date: 11/24/2023
 ms.custom: template-concept 
 ---
 
 # Key concepts for new Azure Load Testing users
 
-Learn about the key concepts and components of Azure Load Testing. This can help you to more effectively set up a load test to identify performance issues in your application.
+Learn about the key concepts and components of Azure Load Testing. This information can help you to more effectively set up a load test to identify performance issues in your application.
 
 ## General concepts of load testing
 
@@ -32,15 +32,15 @@ You can achieve the target number of virtual users by [configuring the number of
 
 ### Ramp-up time
 
-The ramp-up time is the amount of time to get to the full number of [virtual users](#virtual-users) for the load test. If the number of virtual users is 20, and the ramp-up time is 120 seconds, then it will take 120 seconds to get to all 20 virtual users. Each virtual user will start 6 (120/20) seconds after the previous user was started.
+The ramp-up time is the amount of time to get to the full number of [virtual users](#virtual-users) for the load test. If the number of virtual users is 20, and the ramp-up time is 120 seconds, then it takes 120 seconds to get to all 20 virtual users. Each virtual user will start 6 (120/20) seconds after the previous user was started.
 
 ### Response time
 
-The response time of an individual request, or [elapsed time in JMeter](https://jmeter.apache.org/usermanual/glossary.html), is the total time from just before sending the request to just after the last response has been received. The response time doesn't include the time to render the response. Any client code, such as JavaScript, isn't processed during the load test.
+The response time of an individual request, or [elapsed time in JMeter](https://jmeter.apache.org/usermanual/glossary.html), is the total time from just before sending the request to just after the last response is received. The response time doesn't include the time to render the response. Any client code, such as JavaScript, isn't processed during the load test.
 
 ### Latency
 
-The latency of an individual request is the total time from just before sending the request to just after the first response has been received. Latency includes all the processing needed to assemble the request and assembling the first part of the response.
+The latency of an individual request is the total time from just before sending the request to just after the first response is received. Latency includes all the processing needed to assemble the request and assembling the first part of the response.
 
 ### Requests per second (RPS)
 
@@ -54,11 +54,13 @@ Another way to calculate the RPS is based on the average application's [latency]
 
 The formula is: Virtual users = (RPS) * (latency in seconds).
 
-For example, given an application latency of 20 milliseconds (0.02 second), to simulate 100,000 RPS, you should configure the load test with 2,000 virtual users (100,000 * 0.02).
+For example, given an application latency of 20 milliseconds (0.02 seconds), to simulate 100,000 RPS, you should configure the load test with 2,000 virtual users (100,000 * 0.02).
 
 ## Azure Load Testing components
 
-Learn about the key concepts and components of Azure Load Testing.
+Learn about the key concepts and components of Azure Load Testing. The following diagram gives an overview of how the different concepts relate to one another.
+
+:::image type="content" source="./media/concept-load-testing-concepts/azure-load-testing-concepts.png" alt-text="Diagram that shows how the different concepts in Azure Load Testing relate to one another." lightbox="./media/concept-load-testing-concepts/azure-load-testing-concepts-large.png":::
 
 ### Load testing resource
 
@@ -70,16 +72,18 @@ To run a load test for your application, you add a [test](#test) to your load te
 
 You can use [Azure role-based access control](./how-to-assign-roles.md) to grant access to your load testing resource and related artifacts.
 
-Azure Load Testing lets you [use managed identities](./how-to-use-a-managed-identity.md) to access other Azure resources, such as Azure Key Vault for storing [load test secret parameters](./how-to-parameterize-load-tests.md). You can use either a user-assigned or system-assigned managed identity.
+Azure Load Testing lets you [use managed identities](./how-to-use-a-managed-identity.md) to access Azure Key Vault for storing [load test secret parameters or certificates](./how-to-parameterize-load-tests.md). You can use either a user-assigned or system-assigned managed identity.
 
 ### Test
 
-A test represents a load test for your application. A test is attached to an Azure load testing resource. You can create a test in either of two ways:
+A test describes the load test configuration for your application. You add a test to an existing Azure load testing resource.
+
+A test contains a test plan, which describes the steps to invoke the application endpoint. You can define the test plan in either of two ways:
 
-- Create a [test based on an existing JMeter script](./how-to-create-and-run-load-test-with-jmeter-script.md).
-- Create a [URL-based load test](./quickstart-create-and-run-load-test.md) (quick test). Azure Load Testing automatically generates the corresponding JMeter script, which you can modify at any time.
+- [Upload a JMeter test script](./how-to-create-and-run-load-test-with-jmeter-script.md).
+- [Specify the list of URL endpoints to test](./quickstart-create-and-run-load-test.md).
 
-A test contains a JMeter test script, or *test plan*, and related data and configuration files. Azure Load Testing supports all communication protocols that JMeter supports, not only HTTP-based endpoints. For example, you might want to read from or write to a database or message queue in the test script.
+Azure Load Testing supports all communication protocols that JMeter supports, not only HTTP-based endpoints. For example, you might want to read from or write to a database or message queue in the test script.
 
 The test also specifies the configuration settings for running the load test:
 
@@ -88,34 +92,38 @@ The test also specifies the configuration settings for running the load test:
 - [Fail criteria](./how-to-define-test-criteria.md) to determine when the test should pass or fail.
 - Monitoring settings to configure the list of [Azure app components and resource metrics to monitor](./how-to-monitor-server-side-metrics.md) during the test run.
 
-When you start a test, Azure Load Testing deploys the JMeter test script, related files, and configuration to the requested test engine instances. The test engine instances then initiate the JMeter test script to simulate the application load.
+In addition, you can upload CSV input data files and JMeter configuration files to the test.
+
+When you start a test, Azure Load Testing deploys the JMeter test script, related files, and configuration to the test engine instances. The test engine instances then initiate the JMeter test script to simulate the application load.
 
 Each time you start a test, Azure Load Testing creates a [test run](#test-run) and attaches it to the test.
 
-### Test engine
+### Test run
 
-A test engine is computing infrastructure, managed by Microsoft that runs the Apache JMeter test script. The test engine instances run the JMeter script in parallel. You can [scale out your load test](./how-to-high-scale-load.md) by configuring the number of test engine instances. Learn how to configure the number of [virtual users](#virtual-users), or simulate a target number of [requests per second](#requests-per-second-rps).
+A test run represents one execution of a load test. When you run a test, the test run contains a copy of the configuration settings from the associated test.
 
-The test engines are hosted in the same location as your Azure Load Testing resource. You can configure the Azure region when you create the Azure load testing resource.
+After the test run completes, you can [view and analyze the load test results in the Azure Load Testing dashboard](./tutorial-identify-bottlenecks-azure-portal.md) in the Azure portal. 
 
-While the test script runs, Azure Load Testing collects and aggregates the Apache JMeter worker logs from all test engine instances. You can [download the logs for analyzing errors during the load test](./how-to-diagnose-failing-load-test.md).
+Alternately, you can [download the test logs](./how-to-diagnose-failing-load-test.md#download-apache-jmeter-worker-logs-for-your-load-test) and [export the test results file](./how-to-export-test-results.md).
 
-### Test run
+> [!IMPORTANT]
+> When you update a test, the existing test runs don't automatically inherit the new settings from the test. The new settings are only used by new test runs when you run the *test*. If you rerun an existing *test run*, the original settings of the test run are used.
+
+### Test engine
 
-A test run represents one execution of a load test. It collects the logs associated with running the Apache JMeter script, the [load test YAML configuration](./reference-test-config-yaml.md), the list of [app components to monitor](./how-to-monitor-server-side-metrics.md), and the [results of the test](./how-to-export-test-results.md).
+A test engine is computing infrastructure, managed by Microsoft that runs the Apache JMeter test script. The test engine instances run the JMeter script in parallel. You can [scale out your load test](./how-to-high-scale-load.md) by configuring the number of test engine instances. Learn how to configure the number of [virtual users](#virtual-users), or simulate a target number of [requests per second](#requests-per-second-rps).
 
-You can [view and analyze the load test results in the Azure Load Testing dashboard](./tutorial-identify-bottlenecks-azure-portal.md) in the Azure portal.
+The test engines are hosted in the same location as your Azure Load Testing resource. You can configure the Azure region when you create the Azure load testing resource.
 
-> [!IMPORTANT]
-> Existing test runs don't use the new settings when you update a test. When you rerun an existing test run, the initial configuration of the test run is used. The new settings will only be used when you run the test.
+While the test script runs, Azure Load Testing collects and aggregates the Apache JMeter worker logs from all test engine instances. You can [download the logs for analyzing errors during the load test](./how-to-diagnose-failing-load-test.md).
 
 ### App component
 
 When you run a load test for an Azure-hosted application, you can monitor resource metrics for the different Azure application components (server-side metrics). While the load test runs, and after completion of the test, you can [monitor and analyze the resource metrics in the Azure Load Testing dashboard](./how-to-monitor-server-side-metrics.md).
 
 When you create or update a load test, you can configure the list of app components that Azure Load Testing will monitor. You can modify the list of default resource metrics for each app component.
 
-Learn more about which [Azure resource types are supported by Azure Load Testing](./resource-supported-azure-resource-types.md).
+Learn more about which [Azure resource types that Azure Load Testing supports](./resource-supported-azure-resource-types.md).
 
 ### Metrics
 
@@ -125,7 +133,7 @@ During a load test, Azure Load Testing collects metrics about the test execution
 
 - *Server-side metrics* are available for Azure-hosted applications and provide information about your Azure [application components](#app-component). Azure Load Testing integrates with Azure Monitor, including Application Insights and Container insights, to capture details from the Azure services. Depending on the type of service, different metrics are available. For example, metrics can be for the number of database reads, the type of HTTP responses, or container resource consumption.
 
-## Next steps
+## Related content
 
 You now know the key concepts of Azure Load Testing to start creating a load test.
 

articles/load-testing/how-to-assign-roles.md

@@ -6,7 +6,7 @@ ms.author: nicktrog
 services: load-testing
 ms.service: load-testing
 ms.topic: how-to 
-ms.date: 11/07/2022
+ms.date: 11/24/2023
 ms.custom: template-how-to
 ---
 
@@ -32,7 +32,7 @@ In Azure Load Testing, access is granted by assigning the appropriate Azure role
 
 If you have the **Owner**, **Contributor**, or **Load Test Owner** role at the subscription level, you automatically have the same permissions as the **Load Test Owner** at the resource level.
 
-You'll encounter this message if your account doesn't have the necessary permissions to manage tests.
+You encounter this message if your account doesn't have the necessary permissions to manage tests.
 
 :::image type="content" source="media/how-to-assign-roles/azure-load-testing-not-authorized.png" lightbox="media/how-to-assign-roles/azure-load-testing-not-authorized.png" alt-text="Screenshot that shows an error message in the Azure portal that you're not authorized to use the Azure Load Testing resource.":::
 
@@ -41,7 +41,7 @@ You'll encounter this message if your account doesn't have the necessary permiss
 
 ## Role permissions
 
-The following tables describe the specific permissions given to each role. This can include Actions, which give permissions, and Not Actions, which restrict them.
+The following tables describe the specific permissions given to each role. These permissions can include *Actions*, which give permissions, and *Not Actions*, which restrict them.
 
 ### Load Test Owner
 
@@ -125,7 +125,7 @@ You can also configure role-based access to a load testing resource using the fo
     Get-AzRoleDefinition -Name 'Load Test Contributor'
     ```
     
-    The following is the example output:
+    The following snippet is the example output:
 
     ```output
     Name             : Load Test Contributor
@@ -139,7 +139,7 @@ You can also configure role-based access to a load testing resource using the fo
     AssignableScopes : {/}
     ```
 
-* [Get-AzRoleAssignment](/powershell/module/az.resources/get-azroleassignment) lists Azure role assignments at the specified scope. Without any parameters, this cmdlet returns all the role assignments made under the subscription. Use the `ExpandPrincipalGroups` parameter to list access assignments for the specified user, as well as the groups that the user belongs to.
+* [Get-AzRoleAssignment](/powershell/module/az.resources/get-azroleassignment) lists Azure role assignments at the specified scope. Without any parameters, this cmdlet returns all the role assignments made under the subscription. Use the `ExpandPrincipalGroups` parameter to list access assignments for the specified user, and the groups that the user belongs to.
 
     **Example**: Use the following cmdlet to list all the users and their roles within a load testing resource.
 
@@ -163,7 +163,7 @@ You can also configure role-based access to a load testing resource using the fo
     Remove-AzRoleAssignment -SignInName <sign-in Id of a user you wish to remove> -RoleDefinitionName 'Load Test Reader' -Scope '/subscriptions/<SubscriptionID>/resourcegroups/<Resource Group Name>/Providers/Microsoft.LoadTestService/loadtests/<Load Testing resource name>'
     ```
 
-## Next steps
+## Related content
 
 * Learn more about [Using managed identities](./how-to-use-a-managed-identity.md).
 * Learn more about [Identifying performance bottlenecks (tutorial)](./tutorial-identify-bottlenecks-azure-portal.md).