I don't see my dynamic threshold settings in the cfg file of the probe that I am setting up. Say I wany dynamic thresholds for all of my filesystems how do I set this configuration and send it to multiple agents at once?
I'm just starting to move to versions that support dynamic thresholds, so I'm not completely sure how it works. My understand, however, is that it's based on qos monitors, which don't operate at the robot level at all. Therefore, I think to enable this for all servers, I think you should look into configuring baseline_engine and qos_processor.
If someone is more familiar with this and can explain exactly how it works, I'd appreciate that too
What jonhcw said. Not really looked into it much myself yet as I dislike the current implementation of it, but my understanding as well is that you need to look into the baseline_engine probes. Which looks at all the qos_messages to generate the baselines.
I've never tried to configure an alarm from it tho.
you cannot do it currently. All those dynamic thresholds are checked centrally in baseline_engine and are only confguralbe through admin console, configs are in nimsoft database (somewhere there I think). In some next release there will be a feature called policy based monitoring that actually will enabe these kind of "central configuration delpoyments".
Currentyl, one by one, manually, unfortunately.
java -cp ".;lib/*" com.nimsoft.threshold.cmd.ThresholdSetter -user <user> -pwd <password> -probe <probepath> -id <metric id> -threshType <static | dynamic> -type <percent | scalar | stdev> -o <operator> [ -operator1 <operator> | -operator2 <operator> | -operator3 <operator> | -operator4 <operator> | -operator5 <operator> ] [ -level1 <value> | -level2 <value> | -level3 <value> | <-level4> <value> | -level5 <value> ] -subsysId <subsysId> [ -customAlarmMessage <message> ] [ -customClearAlarmMessage <message> ] [ -queue ]
-user user name
-probe path to the baseline_engine probe, e.g. /domain/hub/robot/baseline_engine
-threshType the type of threshold either static or dynamic
-id the metric id of the QOS that thresholds are being defined.
-type thresholds can be a scalar value, percent or stdev of the baseline.
-o the operator values are one of the following L, LE, G, GE, EQ, NE
L is less than
LE is less than or equal
G is greater than
GE is greater than or equal
EQ is equal
NE is not equal
-o takes precedence over any of -operator1, -operator2, -operator3, -operator4, -operator5
-operator1 info alarm threshold operator
-operator2 warn alarm threshold operator
-operator3 minor alarm threshold operator
-operator4 major alarm threshold operator
-operator5 critical alarm threshold operator
if you specify any of operators 1 - 5, you must specify them all
-level1 info alarm threshold value
-level2 warn alarm threshold value
-level3 minor alarm threshold value
-level4 major alarm threshold value
-level5 critical alarm threshold value
note: values are represented as doubles, e.g. the double value for 50% is expressed as 50.0
note: a threshold requires at least one level of alarm threshold value
-subsysId subsystem id for alarm
-threshID optional unique id number to distinguish multiple thresholds of the same threshType and metric ID.
-delete remove the threshold identified by the id, threshType, and threshId
-customAlarmMessage custom message to use in the alarm message for the threshold
-customClearAlarmMessage custom message to use in the clear alarm message for the threshold
-queue send configurations over the BASELINE_CONFIG queue instead of using callbacks
Retrieving data ...