You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/load-testing/how-to-assign-roles.md
+7-3Lines changed: 7 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,8 +32,8 @@ In Azure Load Testing, access is granted by assigning the appropriate Azure role
32
32
33
33
| Role | Description |
34
34
| --- | --- |
35
-
|**Load Test Reader**| Read-only actions in the Load Testing resource. Readers can list and view testsand test runs in the resource. Readers can't create, update, or run tests. |
36
-
|**Load Test Contributor**| View, create, edit, or delete (where applicable) testsand test runs in a Load Testing resource. |
35
+
|**Load Test Reader**| Read-only actions in the Load Testing resource. Readers can list and view tests, test runs, test profiles and test profile runs in the resource. Readers can't create, update, or run tests and test profiles. |
36
+
|**Load Test Contributor**| View, create, edit, or delete (where applicable) tests, test runs, test profiles and test profile runs in a Load Testing resource. |
37
37
|**Load Test Owner**| Full access to the Load Testing resource, including the ability to view, create, edit, or delete (where applicable) assets in a resource. For example, you can modify or delete the Load Testing resource. |
38
38
39
39
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.
@@ -59,7 +59,7 @@ A Load Test Owner can manage everything, including access. The following table s
59
59
60
60
| DataActions | Description |
61
61
| ------- | ----------- |
62
-
| Microsoft.LoadTestService/loadtests/*| Start, stop, and manage load tests. |
62
+
| Microsoft.LoadTestService/loadtests/*| Start, stop, manage load tests and test profiles. |
63
63
64
64
### Load Test Contributor
65
65
@@ -76,6 +76,8 @@ A Load Test Contributor can manage everything except access. The following table
76
76
| DataActions | Description |
77
77
| ------- | ----------- |
78
78
| Microsoft.LoadTestService/loadtests/*| Start, stop, and manage load tests. |
79
+
| Microsoft.LoadTestService/testProfiles/*| Create and manage load test profiles. |
80
+
| Microsoft.LoadTestService/testProfileRuns/*| Start, stop, and manage load test profile runs. |
79
81
80
82
### Load Test Reader
81
83
@@ -92,6 +94,8 @@ A Load Test Reader can view all the resources in a load testing resource but can
Copy file name to clipboardExpand all lines: articles/load-testing/how-to-compare-multiple-test-runs.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,13 +12,13 @@ ms.topic: how-to
12
12
13
13
# Compare load test runs in Azure Load Testing
14
14
15
-
In this article, you learn how you can compare test runs in Azure Load Testing. You can view trends across the last 10 test runs, or you can select and compare up to five individual test runs. Optionally, you can mark a test run as a baseline to compare against.
15
+
In this article, you learn how you can compare test runs in Azure Load Testing. You can view trends across the last 10 test runs, or you can select and compare up to ten individual test runs. Optionally, you can mark a test run as a baseline to compare against.
16
16
17
17
To identify regressions over time, you can use the client-side metrics trends of the last 10 test runs, such as the response time, error rate, and more. In combination with [CI/CD integration](./quickstart-add-load-test-cicd.md), the trends data might help you identify which application build introduced a performance issue.
18
18
19
19
When you want to compare the client-side metrics trends against a specific reference test run, you can mark that test run as your baseline. For example, before you implement performance optimizations in your application, you might first create a baseline load test run, and then validate the effects of your optimizations against your baseline.
20
20
21
-
To compare both client-side and server-side metrics, you can select up to five test runs, and compare them in the Azure Load Testing dashboard. The dashboard overlays the client-side and server-side metric graphs for each test run. By also comparing server-side application metrics in the dashboard, you can identify which application component was the root cause for a sudden performance degradation.
21
+
To compare both client-side and server-side metrics, you can select up to ten test runs, and compare them in the Azure Load Testing dashboard. The dashboard overlays the client-side and server-side metric graphs for each test run. By also comparing server-side application metrics in the dashboard, you can identify which application component was the root cause for a sudden performance degradation.
22
22
23
23
## Prerequisites
24
24
@@ -28,7 +28,7 @@ To compare both client-side and server-side metrics, you can select up to five t
28
28
29
29
## Compare multiple load test runs
30
30
31
-
To compare test runs in Azure Load Testing, you first have to select up to five runs within a load test. You can only compare runs that belong to the same load test. After you select the test runs you want to compare, you can visually compare the client-side and server-side metrics for each test run in the load test dashboard.
31
+
To compare test runs in Azure Load Testing, you first have to select up to ten runs within a load test. You can only compare runs that belong to the same load test. After you select the test runs you want to compare, you can visually compare the client-side and server-side metrics for each test run in the load test dashboard.
32
32
33
33
A test run needs to be in the *Done*, *Stopped*, or *Failed* state to compare it.
34
34
@@ -45,7 +45,7 @@ Use the following steps to select the test runs:
45
45
46
46
1. Select two or more test runs, and then select **Compare** to compare test runs.
47
47
48
-
You can choose a maximum of five test runs to compare.
48
+
You can choose a maximum of ten test runs to compare.
49
49
50
50
:::image type="content" source="media/how-to-compare-multiple-test-runs/compare-test-results-from-list.png" alt-text="Screenshot that shows a list of test runs and the 'Compare' button in the Azure portal." lightbox="media/how-to-compare-multiple-test-runs/compare-test-results-from-list.png":::
Copy file name to clipboardExpand all lines: articles/load-testing/how-to-configure-customer-managed-keys.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -41,18 +41,18 @@ Azure Load Testing uses the customer-managed key to encrypt the following data i
41
41
42
42
- Azure Load Testing can't automatically rotate the customer-managed key to use the latest version of the encryption key. You should update the key URI in the resource after the key is rotated in the Azure Key Vault.
43
43
44
-
## Configure your Azure key vault
44
+
## Configure your Azure Key Vault
45
45
46
46
To use customer-managed encryption keys with Azure Load Testing, you need to store the key in Azure Key Vault. You can use an existing key vault or create a new one. The load testing resource and key vault may be in different regions or subscriptions in the same tenant.
47
47
48
48
Make sure to configure the following key vault settings when you use customer-managed encryption keys.
49
49
50
50
### Configure key vault networking settings
51
51
52
-
If you restricted access to your Azure key vault by a firewall or virtual networking, you need to grant access to Azure Load Testing for retrieving your customer-managed keys. Follow these steps to [grant access to trusted Azure services](/azure/key-vault/general/overview-vnet-service-endpoints#grant-access-to-trusted-azure-services).
52
+
If you restricted access to your Azure Key Vault by a firewall or virtual networking, you need to grant access to Azure Load Testing for retrieving your customer-managed keys. Follow these steps to [grant access to trusted Azure services](/azure/key-vault/general/overview-vnet-service-endpoints#grant-access-to-trusted-azure-services).
53
53
54
54
> [!IMPORTANT]
55
-
> Retrieving customer-managed keys from a private Azure key vault that has access restrictions is currently not supported in **US Gov Virginia** region.
55
+
> Retrieving customer-managed keys from a private Azure Key Vault that has access restrictions is currently not supported in **US Gov Virginia** region.
56
56
57
57
### Configure soft delete and purge protection
58
58
@@ -147,7 +147,7 @@ az keyvault key create \
147
147
148
148
When you use customer-managed encryption keys, you have to specify a user-assigned managed identity. The user-assigned managed identity for accessing the customer-managed keys in Azure Key Vault must have appropriate permissions to access the key vault.
149
149
150
-
1. In the [Azure portal](https://portal.azure.com), go to the Azure key vault instance that you plan to use to host your encryption keys.
150
+
1. In the [Azure portal](https://portal.azure.com), go to the Azure Key Vault instance that you plan to use to host your encryption keys.
0 commit comments