Using NAME to identify an alert in the logical "and" type alert
In this example, the names of the inbound latency alert and the inbound message queue alerts are used to create a logical alert. This alert starts forwarding for conn_1.
- Alert Name: EX3A_c1Slow
- Alert Type: iblat
- Source: conn_1
- Source Count: all
- Comparing: >5
- Duration: once
- Repeating: N seconds for 30
- Action type: none
- Alert Name: EX3B_c1QDLimit
- Alert Type: ipque
- Source: conn_1
- Source Count: all
- Comparing: >15
- Duration: N seconds for 30
- Action type: none
- Alert Name: EX3C_forwardingC1
- Alert Type: and
- Source: EX3A_c1Slow EX3B_c1QDLimit
- Source Count: all
- Comparing: == and true
- Duration: once
- Action type: exec {hcicmd.pl -p process_1 -c "conn_1 fwd_start"}