Help Center > > User Guide> Alarm Center> Creating Notification Rules

Creating Notification Rules

Updated at: Mar 17, 2020 GMT+08:00

Application Operations Management (AOM) supports alarm notification. You can use this function by creating notification rules. When alarms are reported due to an exception in AOM or external services, alarm information can be sent to specified personnel by email or Short Message Service (SMS) message. In this way, these personnel can rectify faults in time to avoid service loss.

If no notification rules exist, no alarm notifications will be sent. In this case, you can only view alarms on the Alarms page in the AOM console.


Alarm notifications are sent by cluster. Alarms that are sent together must be of the same type. You can send a certain type of alarms of a cluster to specified personnel by email or SMS message. Table 1 lists the alarms that support notification.

Table 1 Alarm types

Alarm Type



All types of alarms, including the built-in AOM alarms and alarms registered with AOM by external services.

Built-in AOM alarms

(including ICAgent installation alarms and threshold alarms)

  • ICAgent installation alarms: include the alarms generated when the ICAgent is abnormal or fails to be installed, upgraded, or uninstalled.
  • Threshold alarms: are generated based on threshold rules.

Alarms registered with AOM by external services

For example, node database alarms registered by Blockchain Service (BCS), or probe hibernation alarms registered by Application Performance Management (APM).

More types of alarms are being developed.


After notification rules are created, SMS messages or emails are sent when the notification rules are met.

For example, to ensure that O&M personnel can receive notifications by email when the ICAgent on HostA, HostB, HostC, or HostD in Cluster1 is abnormal or fails to be installed, upgraded, or uninstalled, perform the following operations:

  1. Log in to the AOM console. In the navigation pane, choose Alarm Center > Notification Rules. Then, click Create Notification Rule in the upper right corner.
  2. Click Create SMN Topic and set a notification policy on the Simple Message Notification (SMN) console when AOM is interconnected with SMN. If you have configured a notification policy, skip this step.

    1. Create a topic according to Creating a Topic.

      For example, create a topic named Topic1.

    2. Set a topic policy according to Configuring Topic Policies.

      Select APM for Services that can publish messages to this topic. Otherwise, notifications will fail to be sent.

    3. Add a subscriber, that is, the email or SMS message recipient, for the topic according to Adding a Subscription. SMN can notify subscribers of alarm information in real time.

      For example, enter the email addresses of O&M personnel.

  3. Create a notification rule. Enter a rule name, select an alarm type (for details, see Table 1), select the topic created in step 2, select a target cluster, and click Create.

    For example, set the value of Rule Name to Notification_Rule1, that of Alarm Type to Collector Installation Failure, and that of Topic to Topic1, and select Cluster1, as shown in Figure 1.

    Figure 1 Creating a notification rule

    After the notification rule is created, if the ICAgent on any host in Cluster1 is abnormal or fails to be installed, upgraded, or uninstalled, O&M personnel will receive alarm notifications by email.

More Operations

After creating a notification rule, you can also perform the operations described in Table 2.

Table 2 Related operations



Modifying a notification rule

Click Modify in the Operation column.

Deleting a notification rule

  • To delete a notification rule, click Delete in the Operation column.
  • To delete one or more notification rules, select it or them and click Delete above the rule list.

Searching for a notification rule

Enter a keyword in the search box in the upper right corner and click .

Did you find this page helpful?

Submit successfully!

Thank you for your feedback. Your feedback helps make our documentation better.

Failed to submit the feedback. Please try again later.

Which of the following issues have you encountered?

Please complete at least one feedback item.

Content most length 200 character

Content is empty.

OK Cancel