Ns HTTP Test
This test monitors HTTP connections handled by the NetScaler appliance, and reveals whether all HTTP requests have been responded to, and whether any incomplete requests/responses have been received/sent by the NetScaler.
Target of the test : A Citrix NetScaler Appliance
Agent deploying the test : An external agent
Outputs of the test : One set of results for every Citrix NetScaler being monitored
|
Measurement | Description | Measurement Unit | Interpretation |
---|---|---|---|
New HTTP requests |
Indicates the number of new HTTP requests to the NetScaler device in the last measurement period. |
Number |
This is an indicator of workload on the NetScaler device. |
HTTP 1.0 requests |
Indicates the number of new HTTP v 1.0 requests to the NetScaler device in the last measurement period. |
Number |
Since HTTP 1.0 connections are not capable of providing information about the client's ability to accept compressed data, which is one of the features of the NetScaler devices, it is important to be able to monitor the number of HTTP 1.0 connections relative to the the total connections. |
Requests with incomplete headers |
Indicates the number of incomplete HTTP header received in the last measurement period with incomplete headers. |
Number |
The NetScaler performs content filtering by inspecting every incoming request according to user-configured rules, which are based on HTTP headers. If these headers are incomplete, the NetScaler would not be able to interpret the rules correctly, thus exposing the server to potential attacks. A high value of this measure is hence, undesirable; the reasons for the same should be investigated and the root-cause should be promptly addressed. |
Incomplete HTTP requests |
Indicates the number of incomplete HTTP requests received in the last measurement period. |
Number |
|
Incomplete responses |
Indicates the number of incomplete HTTP responses from the NetScaler device during the last measurement period. |
Number |
This value should typically be small under normal operation. |
Pipelined requests |
Indicates the number of pipelined requests since the last measurement period. |
Number |
HTTP/1.1 allows multiple HTTP requests to be written out to a socket together without waiting for the corresponding responses. The requestor then waits for the responses to arrive in the order in which they were requested. The act of pipelining the requests can result in a dramatic improvement in page loading times, especially over high latency connections. |
Server busy errors |
Indicates number of HTTP requests for which server busy errors were sent during the last measurement period. |
Number |
Ideally, this value should be close to 0. |
Http gets |
Indicates the number of HTTP GETs received during the last measurement period. |
Number |
By analyzing HTTP GET and POST requests and filtering out known bad signatures, you can defend against HTTP-based attacks such as variants of Nimda and Code Red virus.
|
Http posts |
Indicates the number of HTTP POSTs received during the last measurement period. |
Number |
|
HTTP responses |
Indicates the number of new HTTP responses generated from the NetScaler device during the last measurement period. |
Number |
Compare the value of new requests and responses. These values should be close to each other. A significant deviation may indicate a bottleneck or malfunctioning of the NetScaler device. |
HTTP 1.0 responses |
Indicates the number of new HTTP v 1.0 responses sent back during the last measurement period. |
Number |
|