Hold based on queue depth
In this example, if the inbound message queue for ib_tcp_10111 is over 25, this set of alerts holds the flow of the client ob_tcp_10111. The flow is held until the inbound message queue for ib_tcp_10111 is below 10.
- Alert Name: EX14A_overLimit
- Alert Type: ipque
- Source: ib_tcp_10111
- Source Count: all
- Comparing: >25
- Duration: once
- Action type: none
- Alert Name: EX14B_underLimit
- Alert Type: ipque
- Source: ib_tcp_10111
- Source Count: all
- Comparing: <10
- Duration: once
- Action type: none
- Alert Name: EX14C_holding
- Alert Type: hold
- Source: ob_tcp_10111
- Source Count: all
- Comparing: == and true
- Duration: once
- Action type: none
- Alert Name: EX14D_startHold
- Alert Type:and
- Source: EX16A_overLimit !EX14C_holding
- Source Count: all
- Comparing: == and true
- Duration: once
- Action type: exec {hcicmd.pl -p process_1 -c "ob_tcp_10111 phold_obd"}
- Alert Name: EX14E_stopHold
- Alert Type: and
- Source: EX14B_underLimit EX16C_holding
- Source Count: all
- Comparing: == and true
- Duration: once
- Action type: exec {hcicmd.pl -p process_1 -c "ob_tcp_10111 prls_obd"}