| Measurement |
Description |
Measurement
Unit |
Interpretation |
| Connection_rate |
Rate of
connections to the web site. |
Conns/Sec
|
An increase or
decrease in connection rate can represent a change in user workload. |
| Request_rate |
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_xmit_rate |
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_recvd_rate |
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. |
| Pct_errors |
Percentage of
errored responses from the web site. |
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 site’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
|
Responses with a
status code in the range 300-399 can indicate redirects from a server.
Many a time, responses to cached content on the client also falls in
this range. |
| Pct_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. |
| Pct_500_errors |
Percentage of
responses with a status code in the range 500-600. |
Percent
|
Responses in the
range 500-599 are caused by server-side errors (e.g., because of
failures in the server side processing logic). |
| Num_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. |
|
Note:
The
following measures are not available in the Windows version of the
product:
-
Pct_aborts
-
Pct_300s
-
Pct_500_errors
|