You can always set up thresholds for probes without using the web-based configuration. When CA Unified Infrastructure Management (UIM) 8.1 is installed and Probe Provisioning Manager (ppm) v3.0 is running on the secondary hub, here’s the command syntax:
java -cp “.;lib/*” com.nimsoft.threshold.cmd.ThresholdSetter -user <user> -pwd <password> -probe <path> -id <metric id> -threshType <static | dynamic> -type <percent | scalar | stdev> -o <operator> [-level1 <value> | -level2 <value> | -level3 <value> | -level4 <value> | -level5 <value>] -subsysId <subsysId> [-queue]
Note: For linux or unix the path is “.:lib/*”
The options are:
- user: The user name
- pwd: The password
- probe: The path to the baseline_engine probe, for example /domain/hub/robot/baseline_engine
- id: The metric ID of the QoS for which thresholds are being defined.
- threshType: The type of threshold, which is either static or dynamic.
- type: The type of algorithm, which can be percent, scalar, or standard deviation.
- o: One of the following operators:
- L: less than
- G: greater than
- level1: Sets the level1 information alarm threshold value.
- level2: Sets the level2 warning alarm threshold value.
- level3: Sets the level3 minor alarm threshold value.
- level4: Sets the level4 major alarm threshold value.
- level5: Sets the level5 critical alarm threshold value.
- subsysId: The subsystem ID of the QoS for which the thresholds are being defined. Only one subsystem ID can be specified using the subsysId option.
- queue: Indicates to send configurations over the BASELINE_CONFIG queue instead of using callbacks.