SunOne HTTP Test
This test measures the health of the virtual server configured for the Sun Java System Http server.
Target of the test : Any Sun Java System application server
Agent deploying the test : An internal agent
Outputs of the test : One set of results for every virtual server configured for the web server.
| Parameter | Description |
|---|---|
|
Test period |
How often should the test be executed |
|
Host |
The host for which the test is to be configured. |
|
Port |
The port number on which the Sun Java System application server is running. |
|
User |
A valid user name for the Sun Java System server to be monitored. |
|
Password |
Password for the Sun Java System server to be monitored. |
|
Admin Port |
The port number on which the “asadmin” tool runs. |
|
Server |
Name of the Sun Java System server to be monitored. |
|
AppServerDir |
The directory in which Sun Java System application server is installed. |
| Measurement | Description | Measurement Unit | Interpretation |
|---|---|---|---|
|
Request rate |
Rate of requests to the web server during the last measurement period. |
Reqs/Sec |
This measure reflects the server workload. |
|
Data received |
Rate at which the data is received by the server during the last measurement period |
KB/Sec |
|
|
Data transmitted |
Rate at which the data is transmitted by the server during the last measurement period. |
KB/Sec |
|
|
Data transmit high watermark |
The high-water-mark of the data transmit rate by this server |
KB |
|
|
Open connections |
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 connections high water mark |
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. |
|
200 responses |
Percentage of responses with a status code in the range of 200-299 during the last measurement period |
Percent |
|
|
300 responses |
Percentage of responses with a status code in the range of 300-399 during the last measurement period |
Percent |
|
|
400 errors |
Percentage of errors with a status code in the range of 400-499 during the last measurement period |
Percent |
|
|
500 errors |
Percentage of errors with a status code in the range of 500-599 during the last measurement period |
Percent |
|
|
Other responses |
Percentage of responses with a status code that is greater than or equal to 600 during the last measurement period |
Percent |
|
