In public clouds, you can use the NetScaler appliance as a second-tier load balancer when the native load balancer is used as the first tier. The native load balancer can be an application load balancer (ALB) or a network load balancer (NLB). Most of the public clouds do not support UDP health probes in their native load balancers. Hence, if these servers are down their actual status might not be updated. As a result, traffic is sent unconditionally to NetScaler, even if the request cannot be serviced. To monitor the health of such applications, NetScaler supports HTTP and TCP health checks.
An HTTP or TCP listener is created for a content switching virtual server when both the probeProtocol and probePort parameters are configured. The listener reflects the status of the virtual server. The ProbeSuccessResponseCode parameter applies only to HTTP and returns the configured string when the probe is successful.