Set a threshold value for the monitors bound to a service

Last published : Sep 24, 2026
The NetScaler appliance designates a service as UP only when the sum of the weights of all monitors bound to it and that are UP is equal to or greater than the threshold value configured on the service. The weight for a monitor specifies how much that monitor contributes to designating the service to which it is bound as UP.
By default, the monitor threshold is set to 0 and monitor weights are set to 1. All monitors have equal weightage then and a service can go DOWN when any one of the monitors goes DOWN.
For example, assume that three monitors, named Monitor-HTTP-1, Monitor-HTTP-2, and Monitor-HTTP-3 respectively, are bound to Service-HTTP-1, and that the threshold configured on the service is three. Suppose the following weights are assigned to each monitor:
  • The weight of Monitor-HTTP-1 is 1.
  • The weight of Monitor-HTTP-2 is 3.
  • The weight of Monitor-HTTP-3 is 1.
The service is marked UP only when one of the following is true:
  • Monitor-HTTP-2 is UP.
  • Monitor-HTTP-2 and Monitor-HTTP-1 or Monitor-HTTP-3 are UP
  • All three monitors are UP.
Related information

To set the monitor threshold value on a service by using the CLI

At the command prompt, type:
set service <name> -monThreshold <Value>
Example:
set service Service-HTTP-1 -monThreshold 100

To set the monitor threshold value on a service by using the GUI

  1. Navigate to Traffic Management > Load Balancing > Services, and open a service.
  2. In Advanced Settings, select Thresholds & Timeouts, and select Monitor Threshold.