Skip to content

Commit e360f49

Browse files
committed
Update cross-references for renamed file
1 parent 01eedd3 commit e360f49

7 files changed

+9
-9
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -96,7 +96,7 @@ A test engine is computing infrastructure, managed by Microsoft that runs the Ap
9696

9797
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.
9898

99-
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-find-download-logs.md).
99+
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-troubleshoot-failing-test.md).
100100

101101
### Test run
102102

articles/load-testing/how-to-compare-multiple-test-runs.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -102,5 +102,5 @@ When there's a performance issue, you can use the server-side metrics to analyze
102102
## Next steps
103103

104104
- Learn more about [exporting the load test results for reporting](./how-to-export-test-results.md).
105-
- Learn more about [troubleshooting load test execution errors](./how-to-find-download-logs.md).
105+
- Learn more about [troubleshooting load test execution errors](./how-to-troubleshoot-failing-test.md).
106106
- Learn more about [configuring automated performance testing with CI/CD](./tutorial-identify-performance-regression-with-cicd.md).

articles/load-testing/how-to-configure-user-properties.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -124,10 +124,10 @@ Alternately, you also specify properties in the JMeter user interface. The follo
124124

125125
:::image type="content" source="media/how-to-configure-user-properties/jmeter-user-properties.png" alt-text="Screenshot that shows how to reference user properties in the JMeter user interface.":::
126126

127-
You can [download the JMeter errors logs](./how-to-find-download-logs.md) to troubleshoot errors during the load test.
127+
You can [download the JMeter errors logs](./how-to-troubleshoot-failing-test.md) to troubleshoot errors during the load test.
128128

129129
## Next steps
130130

131131
- Learn more about [JMeter properties that Azure Load Testing overrides](./resource-jmeter-property-overrides.md).
132132
- Learn more about [parameterizing a load test by using environment variables and secrets](./how-to-parameterize-load-tests.md).
133-
- Learn more about [troubleshooting load test execution errors](./how-to-find-download-logs.md).
133+
- Learn more about [troubleshooting load test execution errors](./how-to-troubleshoot-failing-test.md).

articles/load-testing/how-to-export-test-results.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ ms.topic: how-to
1414

1515
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.
1616

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 [Troubleshoot test execution errors](./how-to-find-download-logs.md).
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 [Troubleshoot test execution errors](./how-to-troubleshoot-failing-test.md).
1818

1919
You can generate the Apache JMeter dashboard from the CSV log file following the steps mentioned [here](https://jmeter.apache.org/usermanual/generating-dashboard.html#report).
2020

@@ -136,6 +136,6 @@ When you run a load test as part of your CI/CD pipeline, Azure Load Testing gene
136136

137137
## Next steps
138138

139-
- Learn more about [Troubleshooting test execution errors](./how-to-find-download-logs.md).
139+
- Learn more about [Troubleshooting test execution errors](./how-to-troubleshoot-failing-test.md).
140140
- For information about comparing test results, see [Compare multiple test results](./how-to-compare-multiple-test-runs.md).
141141
- To learn about performance test automation, see [Configure automated performance testing](./tutorial-identify-performance-regression-with-cicd.md).

articles/load-testing/how-to-high-scale-load.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ For example, if application latency is 20 milliseconds (0.02 second), and you're
3434
To achieve a target number of requests per second, configure the total number of virtual users for your load test.
3535

3636
> [!NOTE]
37-
> Apache JMeter only reports requests that made it to the server and back, either successful or not. If Apache JMeter is unable to connect to your application, the actual number of requests per second will be lower than the maximum value. Possible causes might be that the server is too busy to handle the request, or that an TLS/SSL certificate is missing. To diagnose connection problems, you can check the **Errors** chart in the load testing dashboard and [download the load test log files](./how-to-find-download-logs.md).
37+
> Apache JMeter only reports requests that made it to the server and back, either successful or not. If Apache JMeter is unable to connect to your application, the actual number of requests per second will be lower than the maximum value. Possible causes might be that the server is too busy to handle the request, or that an TLS/SSL certificate is missing. To diagnose connection problems, you can check the **Errors** chart in the load testing dashboard and [download the load test log files](./how-to-troubleshoot-failing-test.md).
3838
3939
## Test engine instances and virtual users
4040

articles/load-testing/how-to-use-jmeter-plugins.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -132,6 +132,6 @@ To reference the plugin JAR file in the test configuration YAML file:
132132

133133
## Next steps
134134

135-
- Learn how to [Download JMeter logs to troubleshoot a load test](./how-to-find-download-logs.md).
135+
- Learn how to [Download JMeter logs to troubleshoot a load test](./how-to-troubleshoot-failing-test.md).
136136
- Learn how to [Monitor server-side application metrics](./how-to-monitor-server-side-metrics.md).
137137
- Learn how to [Automate load tests with CI/CD](./tutorial-identify-performance-regression-with-cicd.md).

articles/load-testing/resource-limits-quotas-capacity.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -52,7 +52,7 @@ Azure Load Testing captures metrics, test results, and logs for each test run. T
5252
| Server-side metrics | 90 days | Learn how to [configure server-side metrics](./how-to-monitor-server-side-metrics.md). |
5353
| Client-side metrics | 365 days | |
5454
| Test results | 6 months | Learn how to [export test results](./how-to-export-test-results.md). |
55-
| Test log files | 6 months | Learn how to [download the logs for troubleshooting tests](./how-to-find-download-logs.md). |
55+
| Test log files | 6 months | Learn how to [download the logs for troubleshooting tests](./how-to-troubleshoot-failing-test.md). |
5656

5757
## Request quota increases
5858

0 commit comments

Comments
 (0)