-
In the Summary view, scroll down to the table titled Errors and click either the Http Error or the Validation Rule Error.
-
The Load Test Analyzer changes to the Tables view with the Errors table displayed and the rule type that you clicked is selected.
-
In the row for the Validation Rule Error rule type, notice the ValidateResponseurl listed under the SubType error column. This threshold violation was caused by the following highlighted code that you added to the Red.aspx.cs file which randomly causes a mock page delay for up to five seconds:
protected void Page_Load(object sender, EventArgs e)
{
Random rnd = new Random();
int result = rnd.Next(5000);
//To emmulate various page times up to 5 seconds.
Thread.Sleep(result);
if (result < 500)
Response.Redirect("NOWHERE"); //10% chance to cause an HTTP 404 error.
}
This mock delay can potentially violate both the Warning Threshold Value of 3 and the Critical Threshold Value of 4 you specified earlier in the walkthrough. The warning icons are displayed as yellow triangles with an exclamation point in them and the critical violation icons are displayed as red circles with an X in them.
-
In the row for the Http Error error type, notice the 404 - NotFound under the SubType error column. This was caused by the following highlighted code that you added to the Red.aspx.cs file. This code produces a ten per cent chance of redirecting to a nonexistent page, which causes the error:
protected void Page_Load(object sender, EventArgs e)
{
Random rnd = new Random();
int result = rnd.Next(5000);
//To emmulate various page times up to 5 seconds.
Thread.Sleep(result);
if (result < 500)
Response.Redirect("NOWHERE"); //10% chance to cause an HTTP 404 error.
}
-
Under the Count column, click the link the number for the Validation Rule Error rule type.
The Load Test Errors dialog box is displayed.
-
Scroll to the right and under the Details column, click the TestLog link.
-
The Web Performance Test Viewer opens in a separate tab displaying the ColorWebTest associated with the error.
-
Click Close on the Load Test Errors dialog box.
-
Select the LoadTest[time] tab to go back to the Load Test Analyzer that displays the load test results.
-
In the Counters panel, observe that the Scenaro1 node has one of the threshold warning icons on it. Expand the node until you get to the Avg Page Time counter that was impacted by the code that caused the threshold violations.
-
In the Graphs view, notice that the threshold violation icons are also displayed for the threshold violations appearing in the Page Response Time graph.
-
Click the plot line that has the violation icon on it.
-
The plot line is bolded and the Avg Page Time counter is highlighted in the Graphs view Legend for the Red (Reporting name added in previous walkthrough) request.
-
Notice that the Max column for the Avg Page Time counter exceeds the threshold you specified.