%BOOK_ENTITIES; ]>

(NetScaler load balancer only; requires NetScaler version 10.0) Health checks are used in load-balanced applications to ensure that requests are forwarded only to running, available services. When creating a load balancer rule, you can specify a health check policy. This is in addition to specifying the stickiness policy, algorithm, and other load balancer rule options. You can configure one health check policy per load balancer rule. Any load balancer rule defined on a NetScaler load balancer in &PRODUCT; can have a health check policy. The policy consists of a ping path, thresholds to define "healthy" and "unhealthy" states, health check frequency, and timeout wait interval. When a health check policy is in effect, the load balancer will stop forwarding requests to any resources that are found to be unhealthy. If the resource later becomes available again, the periodic health check will discover it, and the resource will once again be added to the pool of resources that can receive requests from the load balancer. You can delete or modify existing health check policies. To configure how often the health check is performed by default, use the global configuration setting lbrule_health check_time_interval. You can override this value for an individual health check policy. For details on how to set a health check policy using the UI, see .