TriggersΒΆ

Triggers are templates where you define the condition and metric. By default, canned or pre-defined triggers are available in Harmony Controller. You can additionally add custom triggers if required. You can set various types o triggers for alerts. Note that Infrastructure and system triggers are available at provider level whereas app service trigger is only available at tenant level. The following types of triggers are available.

  • System: Triggers that are related to the syslogs generated by various modules in ACOS

  • Infrastructure: Triggers related to metrics associated with Thunder devices. These can be at a Cluster-level, Device-level, or a Partition-level

  • App Service: Triggers for the various resources associated with the services provided by A10 such as ADC, CGN, FW, and so on.

Note

Infrastructure and System triggers are available at both provider and tenant level whereas App Service trigger is only available at tenant level.

Category

Sub-Category

System

Health Monitor
Networking
Service Modules
Service Operation
Others

App Service

CGNv6
FW
SLB

Infrastructure

Cluster Device
Cluster Partition

The following are examples of various categories of triggers that are provided as Canned Triggers out-of-the-box in any Harmony installation:

  • Infrastructure

    1. Avg Mem used > 75% and < 90%

      To trigger an alert when the used memory in past five minutes always greater than 75% and less than 90% and notifies the user through email or webhook, only if notification is set-up.

    2. Session Resource used > 50%

      Description: To trigger an alert when the sesssion resource utilization is high - exceeding 50% and notifies the user through email or webhook, only if notification is set-up.

  • App Service

    1. Downlink Subscriber FixedNAT44 Pkt Rate > 1250K pps

      Description: To trigger an alert when the five minute average of Downlink Ingress packet rate is greater than 1250k packets per second for CGN technology Fixed NAT 44 and notifies the user through email or webhook, only if notification is set-up.

    2. HTTP avg Req Rate > 10K

      Description: To trigger an alert when an average HTTP requests are coming at high rate [> 10K RPS] and notifies the user through email or webhook, only if notification is set-up.

    3. FW Pkt Drop > 1% of traffic

      Description: To trigger an alert when the packet drop ratio greater than 0.01 and notifies the user through email or webhook, only if notification is set-up.

  • System

    1. Device came Down

      Description: To trigger an alert when the an ACOS resource is down and notifies the user through email or webhook, only if notification is set-up.

    2. HA Cluster State Transition happened

      Description: To trigger an alert when a HA Cluster has changed its configuration and notifies the user through email or webhook, only if notification is set-up.

    3. VCS Cluster State Change

      Description: To trigger an alert when a VCS Cluster has changed its configuration and notifies the user through email or webhook, only if notification is set-up.

    4. Service on a device is Up

      Description: To trigger an alert when a service on a device is up and notifies the user through email or webhook, only if notification is set-up.

    For detailed information, refer to Canned Triggers for Creating Alerts.