| Measurement |
Description |
Measurement
Unit |
Interpretation |
| Request_rate |
Rate of requests
for a specific transaction |
Reqs/Sec
|
An increase or
decrease in request rate for a specific transaction can represent a
change in the user workload. |
| Pct_errors |
Percentage of
errored responses from the web site for a specific transaction |
Percent
|
Percentage of
responses for the transaction that report a 400 or 500 status code |
| Pct_aborts |
Percentage of
requests aborted by users when accessing a specific transaction from a
web site (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 there has been a significant slow-down or error
when users access a specific transaction (reasons for this could be
errors in the application(s) supporting the transaction, failure of
the backend database, etc.). |
| Data_xmit_rate |
Rate at which the
data is transmitted by the web site in response to user requests for a
specific transaction |
KB/Sec
|
A large increase
in the data transmission rate can be indicative of an increase in the
popularity of a specific transaction. Alternatively, a sudden increase
in data rate may also indicate a change in the characteristics of a
transaction |
| Avg_response_time |
The average time
taken by the web site to respond to requests for a specific
transaction, measured in seconds. Only requests for which successful
responses are received are considered while computing the average
response time. |
Secs
|
An increase in
response time is a major cause for user dissatisfaction with
e-business sites. By correlating an increase in response time with the
other metrics collected by the agent per transaction, an operator can
diagnose the reason(s) for the deterioration in performance. |
| Num_current_requests |
Number of server
threads/processes currently in use for serving requests for the
specific transaction supported by a web site (this measurement is not
available for Apache web servers) |
Number
|
If a majority of
the server threads/processes are in use simultaneously to serve
requests for a specific transaction, this may be indicative of a
server bottleneck caused by the transaction being considered |
|
Note:
The
following measures are not available in the Windows version of the
product:
-
Pct_aborts
-
Num_current_requests
|