| Measurement |
Description |
Measurement
Unit |
Interpretation |
| Request_rate
|
Rate
of requests to the web server |
Reqs/Sec
|
This measure reflects the server workload. |
| Data_rcvd_rate |
Rate
at which the data is received by the server |
KB/Sec
|
|
| Data_xmit_rate |
Rate
at which data is transmitted by the server |
KB/Sec
|
|
| Xmit_rate_hwm |
The
high-water-mark of the data transmit rate of this server |
KB
|
|
| Open_connections_count |
Number
of server threads/processes currently in use for serving requests |
Number
|
Ideally, this measure must be low. Too many server threads or processes serving user requests could indicate a server-side bottleneck - either with the web server itself or with one of the backend components that the web server uses (e.g., database server). |
| Open_conns_hwm |
The
high-water-mark of the open connections count |
Number
|
Changes in the high water mark are indicative of times when the server has been a performance bottleneck. Note that the high water mark value gets reset every time the server is restarted. |
| Pct_200_responses |
Percentage
of responses with a status code in the range of 200-299 |
Percent
|
|
| Pct_300_responses |
Percentage
of responses with a status code in the range of 300-399 |
Percent
|
|
| Pct_400_errors |
Percentage
of errors with a status code in the range of 400-499 |
Percent
|
|
| Pct_500_errors |
Percentage
of errors with a status code in the range of 500-599 |
Percent
|
|
| Pct_other_responses |
Percentage
of responses with a status code that is greater than or equal to 600 |
Percent
|
|