Web Site Test

For each web site configured for monitoring on the target web server, this test reports the load on the web site and how well the site processes the load.

Target of the test : A web site supported by a web server

Agent deploying the test : An internal agent;

Outputs of the test : One set of results for every web site monitored

Configurable parameters for the test
  1. TEST PERIOD - How often should the test be executed .
  2. Host - The host for which the test is to be configured.
  3. Port - The port to which the specified host listens.
Measurements made by the test
Measurement Description Measurement Unit Interpretation

Connections:

Rate of connections to the web site.

Conns/Sec

An increase or decrease in the connection rate can represent a change in the user workload.

Requests:

Rate of requests to the web site.

Reqs/Sec

With the advent of HTTP/1.1, multiple requests can be transmitted over the same TCP connection. The ratio of requests per connection can provide an idea of the effectiveness of the HTTP 1.1 protocol.

Data transmitted:

Rate at which the data is transmitted by the web site in response to user requests.

KB/Sec

A large increase in the data transmission rate can be indicative of an increase in the popularity of a web site hosted on the server.

Data received:

Rate at which the data is received by the web site.

KB/Sec

An increase in this value is indicative of an increase in user requests to the web site.

Errors:

Percentage of error responses from the web site.

Percent

Percentage of responses with a 400 or 500 status code.

400 errors:

Percentage of responses with a status code in the range 400-500.

Percent

An unexpected increase in the percentage of responses with status codes in the range 400-499 can indicate a sudden problem at the server.

Current requests:

Number of server threads/processes currently in use for serving requests for a web site (this measurement is not available for Apache web servers).

Number

A majority of the server threads/processes being used simultaneously to serve requests for a web site may be indicative of a server bottleneck caused by the web site.