Skip to content

Commit 0f62228

Browse files
2,3,4 fix
1 parent 4f93e64 commit 0f62228

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/load-testing/how-to-define-test-criteria.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -167,7 +167,7 @@ In this section, you configure test failure criteria on server-side metrics for
167167
168168
4. Configure the **Metrics reference identity**. The identity can be the system-assigned identity of the load testing resource, or one of the user-assigned identities. Make sure you use the same identity you've granted access previously.
169169
170-
:::image type="content" source="media/how-to-define-test-criteria/moniotring-tab.png" alt-text="Screenshot of configuring metrics reference identity":::
170+
:::image type="content" source="media/how-to-define-test-criteria/monitoring-tab.png" alt-text="Screenshot of configuring metrics reference identity.":::
171171
172172
6. On the **Test criteria** pane, fill the **Resource ID, Namespace, Metric, Aggregation, Condition, Threshold values** for your test. You can set failure criteria only for those resources/app components that you are monitoring during the test.
173173
@@ -179,7 +179,7 @@ When you now run the load test, Azure Load Testing uses the test criteria to det
179179
9. Run the test and view the status in the load test dashboard.
180180
The dashboard shows each of the test criteria and their status. The overall test status is failed if at least one criterion was met.
181181
182-
:::image type="content" source="media/how-to-define-test-criteria/dashboard.png" alt-text="Screenshot of configuring failure criteria on server metrics.":::
182+
:::image type="content" source="media/how-to-define-test-criteria/dashboard.png" alt-text="Screenshot of the dashboard displaying test results.":::
183183
184184
## Auto stop configuration
185185

0 commit comments

Comments
 (0)