How to use a user monitor to check websites
You can configure a user monitor to check for specific website problems that are reported by HTTP servers using specific HTTP codes. The following table lists the HTTP response codes that this user monitor expects.
| HTTP response code | Meaning |
|---|---|
| 200 - success | Probe success. |
| 503 - service unavailable | Probe failure. |
| 404 - not found | Script not found or cannot run. |
| 500 - Internal server error | Internal error/resource constraints in dispatcher (out of memory, too many connections, unexpected system error, or too many processes). The service is not marked DOWN. |
| 400 - bad request | Error parsing HTTP request. |
| 502 - bad gateway | Error decoding script's response. |
You configure the user monitor for HTTP by using the following parameters.
| Parameter | Specifies |
|---|---|
| scriptName | The path and name of the script to run. |
| scriptArgs | The strings that are added in the POST data. They are copied to the request verbatim. |
| dispatcherIP | The IP address of the dispatcher to which the probe is sent. |
| dispatcherPort | The port of the dispatcher to which the probe is sent. |
| localfileName | The name of a monitor script file on the local system. |
| destPath | A particular location on the NetScaler appliance where the uploaded local file is stored. |
To create a user monitor to monitor HTTP, see Configuring Monitors in a Load Balancing Setup.
Related information