IIS anomalies

The IIS collector allows to insert the following types of anomalies in an Anomalies Profile:

Private Bytes

The current number of KBytes the HTTP/ASP service has allocated that cannot be shared with other processes. If this number is consistently large and growing, there is probably a leak in a Server-Side Object. The default anomaly conditions are:

Severity 1: Increase by 10 MB (10000 KB) per hour.
Severity 2: Increase by 20 MB (20000 KB) per hour.
Severity 3: Increase by 30 MB (30000 KB) per hour.

404/sec

Shows the number of pages that are displaying an HTTP 404 result code to client. Anything greater than 0 is an indication of an invalid test run, because the test script is requesting pages that do not exist. The default anomaly conditions are:

Severity 1: > 0
Severity 2: > 10
Severity 3: > 50

Raise Time: 60 seconds.

File Cache Hits %

The ratio of File Cache Hits to total cache requests. The default anomaly conditions are:

Severity 1: < 95 %
Severity 2: < 90 %
Severity 3: < 80 %

Raise Time: 60 seconds.

ASP Errors/sec

The number of errors per second, including connection errors, compile errors, and run-time errors. If this number is greater than 0, something is wrong with the test scripts, server configuration, or scripts in ASP pages. The default anomaly conditions are:

Severity 1: > 0
Severity 2: > 10
Severity 3: > 50

Raise Time: 60 seconds.

ASP Request Not Found/sec

Shows the number of ASP pages that were not found per second. These pages display an HTTP 404 result code to the client. Anything greater than 0 is an indication of an invalid test run, because the test script is requesting pages that do not exist. The default anomaly conditions are:

Severity 1: > 0
Severity 2: > 10
Severity 3: > 50

Raise Time: 60 seconds.

ASP Requests Rejected/sec

The number of requests not executed per second because the queue was full or there were insufficiant resources to meet the number of hits that the Web server is seeing. If this number is greater than 0, the stress test is too heavy, or the ASP pages are too complex. The default anomaly conditions are:

Severity 1: > 0
Severity 2: > 5
Severity 3: > 10

Raise Time: 60 seconds.

ASP Requests Queued

This should remain close to 0 but it will go up and down when testing a heavily scripted ASP page. If the limit is reached, your browser will display "HTTP/1.0 Server Too Busy". If this queue grows rapidly as more stress is applied, this indicates that the ASP pages are too complex. The default anomaly conditions are:

Severity 1: > 5
Severity 2: > 10
Severity 3: > 20

Raise Time: 60 seconds.

ASP Errors During Script Runtime/sec

This is a count of errors per second that occurred in the ASP pages you are requesting. This should always be 0. If it sporadically shows a value greater than 0, look at the IIS log to see which page is causing the problem and check for the error that occurred. If you have the registry set to capture these, the event log will also display the error. The default anomaly conditions are:

Severity 1: > 0
Severity 2: > 5
Severity 3: > 10

Raise Time: 60 seconds.

ASP Cache Hit %
Percent of requests found in template cache. The default anomaly conditions are:

Severity 1: < 95%
Severity 2: < 90%
Severity 3: < 80%

Raise Time: 60 seconds.





Go back to the Learning center:


Copyright © AgileLoad. All rights reserved.
Agile Load testing tool| Contact AgileLoad | Terms of Use | Sitemap