| Measurement |
Description |
Measurement
Unit |
Interpretation |
| Connection_rate |
Rate of
connections to the web server. |
Conns/Sec
|
An increase or
decrease in connection rate can represent a change in user workload. |
| Request_rate |
Rate of requests
to the web server. |
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_xmit_rate |
Rate at which the
data is transmitted by the server. |
KB/Sec
|
A large increase
in the data transmission rate can be indicative of an increase in the
popularity of one or more web sites hosted on the server. |
| Data_recvd_rate |
Rate at which the
data is received by the server. |
KB/Sec
|
An increase in
this value is indicative of an increase in user requests to the server. |
| Pct_errors |
Percentage of
errored responses from the server. |
Percent
|
Percentage of
responses with a 400 or 500 status code. |
| Pct_aborts |
Percentage of
requests aborted by users (a request is deemed to have been aborted if
either the connection is closed without any response being generated,
or if the TCP connection is closed as the server is reading the
request or as it is responding to the request). |
Percent
|
A high percentage
of aborts can happen if the web server’s responsiveness has
dramatically reduced. Aborts may also occur because of backend errors
(e.g., application failures, database connection problems etc.). |
| Pct_300s |
Percentage of
responses with a status code in the range 300-400. |
Percent
|
300 responses
could indicate page caching on the client browsers. Alternatively 300
responses could also indicate redirection of requests. A sudden change
in this value could indicate a problem condition. |
| Pct_400_errors |
Percentage of
responses with a status code in the range 400-500. |
Percent
|
A high value
indicates a number of missing/errored pages. |
| Pct_500_errors |
Percentage of
responses with a status code in the range 500-600. |
Percent
|
Since responses
with a status code of 500-600 indicate server side processing errors,
a high value reflects an error condition. |
| Num_current_requests |
Number of server
threads/processes currently in use for serving requests (this
measurement is not available for Apache web servers). |
Number
|
If a majority of
the server threads/processes are in use simultaneously, this may be
indicative of a server bottleneck. |
|
Note:
The
following measures are not available in the Windows version of the
product:
-
Pct_aborts
-
Pct_300s
-
Pct_500_errors
|