(Click to open topic with navigation)

You are here: 17 Object Triggers > How-to > Requiring an Object Threshold for Trigger Execution

17.6 Requiring an Object Threshold for Trigger Execution

ClosedContext

Threshold triggers allow sites to configure triggers to launch based on internal scheduler statistics, such as generic metrics. For example, you might configure a trigger to warn the administrator when the percentage of nodes available is less than 25.

To configure a threshold trigger

  1. Create a trigger. Set its EType to threshold. Configure the AType, Action, and Threshold attributes' values based on the valid thresholds per object listed in the table found in Threshold Triggers.

    NODECFG[node04] TRIGGER=EType=threshold,AType=exec,Action="$HOME/hightemp.py $OID",Threshold=gmetric

  2. Insert the gmetric name between brackets (such as gmetric[temp]). Provide a comparison operator. For valid options, see the comparison operators table.
  3. Provide a number or string to match against the threshold.

    4. NODECFG[node04] TRIGGER=EType=threshold,AType=exec,Action="$HOME/hightemp.py $OID",Threshold=gmetric[TEMP]>70,RearmTime=5:00

    Moab launches a script that warns the administrator when node04's gmetric temp exceeds 70. Moab rearms the trigger five minutes after it fires.

© 2016 Adaptive Computing