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-export-test-results.md
+19-12Lines changed: 19 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,13 +6,13 @@ services: load-testing
6
6
ms.service: load-testing
7
7
ms.author: nicktrog
8
8
author: ntrogh
9
-
ms.date: 02/10/2023
9
+
ms.date: 02/08/2024
10
10
ms.topic: how-to
11
-
11
+
# CustomerIntent: As a tester, I want to understand how I can export the load test results, so that I can use other reporting tools to analyze the load test results.
12
12
---
13
13
# Export test results from Azure Load Testing for use in third-party tools
14
14
15
-
In this article, you learn how to download the test results from Azure Load Testing in the Azure portal. You might use these results for reporting in third-party tools or for diagnosing test failures. Azure Load Testing generates the test results in comma-separated values (CSV) file format, and provides details of each application request for the load test.
15
+
In this article, you learn how to export your Azure Load Testing test results. You can download the results by using the Azure portal, as an artifact in your CI/CD workflow, in JMeter by using a backend listener, or by copying the results from an Azure storage account. You might use these results for reporting in third-party tools or for diagnosing test failures. Azure Load Testing generates the test results in comma-separated values (CSV) file format, and provides details of each application request for the load test.
16
16
17
17
You can also use the test results to diagnose errors during a load test. The `responseCode` and `responseMessage` fields give you more information about failed requests. For more information about investigating errors, see [Diagnose failing load tests](./how-to-diagnose-failing-load-test.md).
18
18
@@ -23,7 +23,7 @@ You can generate the Apache JMeter dashboard from the CSV log file following the
23
23
- An Azure account with an active subscription. If you don't have an Azure subscription, [create a free account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F) before you begin.
24
24
- An Azure Load Testing resource that has a completed test run. If you need to create an Azure Load Testing resource, see [Create and run a load test](./quickstart-create-and-run-load-test.md).
25
25
26
-
## Test results file
26
+
## Test results file format
27
27
28
28
Azure Load Testing generates a test results CSV file for each [test engine instance](./concept-load-testing-concepts.md#test-engine). Learn how you can [scale out your load test](./how-to-high-scale-load.md).
After a load test run finishes, you can access and download the load test results through the Azure portal, or as an artifact in your CI/CD workflow.
44
+
42
45
>[!IMPORTANT]
43
46
>For load tests with more than 45 engine instances or a greater than 3-hour test run duration, the results file is not available for download. You can [configure a JMeter Backend Listener to export the results](#export-test-results-using-jmeter-backend-listeners) to a data store of your choice or [copy the results from a storage account container](#copy-test-artifacts-from-a-storage-account-container).
47
+
44
48
# [Azure portal](#tab/portal)
45
49
46
50
To download the test results for a test run in the Azure portal:
@@ -134,16 +138,19 @@ When you run a load test as part of your CI/CD pipeline, Azure Load Testing gene
134
138
135
139
:::image type="content" source="./media/how-to-export-test-results/azure-pipelines-run-summary.png" alt-text="Screenshot that shows the Azure Pipelines workflow summary page, highlighting the test results in the Stages section." lightbox="./media/how-to-export-test-results/azure-pipelines-run-summary.png":::
136
140
---
137
-
## Export test results using JMeter Backend Listeners
138
-
You can use [JMeter Backend Listeners](https://jmeter.apache.org/usermanual/component_reference.html#Backend_Listener) to export test results to databases like InfluxDB, MySQL or monitoring tools like AppInsights.
139
141
140
-
You can use the backend listeners available by default in JMeter, backend listeners from [jmeter-plugins.org](https://jmeter-plugins.org), or a custom backend listener in the form of a Java archive (JAR) file.
142
+
## Export test results using JMeter backend listeners
141
143
142
-
A sample JMeter script that uses a [backend listener for Azure Application Insights](https://github.com/adrianmo/jmeter-backend-azure) is available [here](https://github.com/Azure-Samples/azure-load-testing-samples/tree/main/jmeter-backend-listeners).
144
+
You can use a [JMeter backend listener](https://jmeter.apache.org/usermanual/component_reference.html#Backend_Listener) to export test results to databases like InfluxDB, MySQL, or monitoring tools like Azure Application Insights.
145
+
146
+
You can use the default JMeter backend listeners, backend listeners from [jmeter-plugins.org](https://jmeter-plugins.org), or a custom backend listener in the form of a Java archive (JAR) file.
147
+
148
+
The following code snippet shows an example of how to use the backend listener for Azure Application Insights, in a JMeter file (JMX):
143
149
144
-
The following code snippet shows an example of a backend listener, for Azure Application Insights, in a JMX file:
You can download the full [example of using the Azure Application Insights backend listener](https://github.com/Azure-Samples/azure-load-testing-samples/tree/main/jmeter-backend-listeners).
153
+
147
154
## Copy test artifacts from a storage account container
148
155
149
156
>[!IMPORTANT]
@@ -176,8 +183,8 @@ To copy the test results and log files for a test run from a storage account, in
176
183
177
184
The SAS URL is valid for 60 minutes from the time it gets generated. If the URL expires, select **Copy artifacts** to generate a new SAS URL.
178
185
179
-
## Next steps
186
+
## Related content
180
187
181
188
- Learn more about [Diagnosing failing load tests](./how-to-diagnose-failing-load-test.md).
182
-
- For information about comparing test results, see [Compare multiple test results](./how-to-compare-multiple-test-runs.md).
183
-
- To learn about performance test automation, see [Configure automated performance testing](./quickstart-add-load-test-cicd.md).
189
+
- Learn more about [Comparing multiple test results](./how-to-compare-multiple-test-runs.md).
190
+
- Learn more about [Configuring automated performance testing in Azure Pipelines](./quickstart-add-load-test-cicd.md).
0 commit comments