Creation Methods

Static threshold rules are classified into single- and multi-resource static threshold rules based on the mapping between resources and rules.

• Single-resource static threshold rules: Resources and rules have a many-to-many relationship. When multiple resources are monitored, multiple rules are generated after the creation is complete. Each resource can be monitored by using an independent rule.

  To monitor resources separately, you are advised to use this method. For details, see Directly Creating Static Threshold Rules.

• Multi-resource static threshold rules: Resources and rules have a many-to-one relationship. When multiple resources are monitored, only one rule is generated after the creation is complete. Multiple resources are monitored by the same rule.

  To monitor multiple resources in a centralized manner, you are advised to use this method.

  • Based on O&M experience, AOM provides default multi-resource threshold rules for key metrics (including CPU usage, physical memory usage, host status, and service status) of all hosts and services. You can create default multi-resource threshold rules in one click. For details, see Creating Multi-Resource Threshold Rules.
  • If default multi-resource threshold rules cannot meet requirements, use static threshold templates to create rules. For details, see Using Templates to Create Static Threshold Rules. Static threshold templates are used for creating multi-resource static threshold rules. For details on how to create a static threshold template, see Creating a Static Threshold Template.

Precautions

• You can create a maximum of 1000 static threshold rules. If the number of static threshold rules reaches 1000, delete unnecessary rules and create new ones.
• Setting a notification policy
  If you want to send notifications by email or Short Message Service (SMS) message when the static threshold rule status (Exceeded, Normal, or Insufficient) changes, set a notification policy on the Simple Message Notification (SMN) console according to the following procedure. If you do not need to receive email or SMS notifications, skip the following operations. The procedure is as follows:

  1. Create a topic according to Creating a Topic.
  2. Set a topic policy according to Configuring Topic Policies.

     Select APM for Services that can publish messages to this topic. If APM is not selected, notifications cannot be sent.

  3. Add a subscriber, that is, the email or SMS message recipient, for the topic according to Adding a Subscription.

Directly Creating Static Threshold Rules

1. Log in to the AOM console. In the navigation pane, choose Alarm Center > Threshold Rules. Then, click Add Threshold in the upper right corner.
2. Customize static threshold rules.
   1. Select a resource: Enter a threshold name, select Custom creation for Creation Mode, select a resource type, select the resource to be monitored from the resource tree, and click Next.
      

      • You can select a maximum of 100 resources from the resource tree.
      • When multiple resources are selected, multiple single-resource static threshold rules will be created after the creation is complete. Each resource is monitored by a single-resource static threshold rule. A rule name consists of the threshold rule name you enter in the Threshold name text box, and a sequence number ranging from 0 to 9. The earlier a resource is selected, the smaller its number.
      Figure 1 Selecting resources
      
   2. Define a threshold: Select the metric to be monitored, and set parameters such as Threshold Condition, Consecutive Period, Alarm Severity, Statistic Method, and Send Notification.
      

      • Threshold Condition: trigger condition of a threshold alarm. A threshold condition consists of two parts: determination condition (≥, ≤, >, or <) and threshold value. For example, after Threshold Condition is set to > 85, if the actual metric value exceeds 85, a threshold alarm is generated.
      • Consecutive Period: If a metric value meets the threshold condition for a specified number of consecutive periods, a threshold alarm is generated.
      • Statistic Method: method used to measure metric values.
      • Statistical Cycle: interval at which metric data is collected.
      • Send Notification: whether to send notifications by email or SMS message when the static threshold rule status (Exceeded, Normal, or Insufficient) changes.
        • If you want to receive email or SMS notifications, select Yes, set a notification policy, select a created topic, and select a trigger scenario.
        • If you do not need to receive notifications by email or SMS message, select No.
      • Trigger Scenario: condition for sending a notification.

        You can select multiple trigger conditions. For example, to receive notifications if the threshold status changes to Exceeded, select Threshold crossing. To receive notifications upon any threshold status change, select all trigger conditions.

      Figure 2 Customizing a threshold
      

3. Click Submit. As shown in the following figure, multiple single-resource static threshold rules are created. One resource corresponds to one rule. Each resource can be monitored by using an independent rule.

   A single-resource static threshold rule monitors a host. If the CPU usage of the host exceeds 85%, a threshold alarm is generated on the alarm page. You can choose Alarm Center > Alarm List in the navigation pane and view the alarm in the alarm list. If the host meets the preset notification policy, an email or SMS message will be sent.

   Figure 3 Creating a single-resource static threshold rule
   

Using Templates to Create Static Threshold Rules

Before creating a static threshold, ensure that a static threshold template has been created according to Creating a Static Threshold Template.

1. Log in to the AOM console. In the navigation pane, choose Alarm Center > Threshold Rules. Then, click Add Threshold in the upper right corner.
2. Select a resource: Enter a threshold rule name, select Template importing for Creation Mode, select a resource type, select the resource to be monitored from the resource tree, and click Next.
   

   • When the option below Resource Type is disabled (that is, ): Select up to 100 resources from the resource tree.
   • When the option below Resource Type is enabled (that is, ): If Resource Type is Host, all hosts will be monitored. If Resource Type is Component, all components will be monitored. Your setting also applies to hosts and components added later.
   Figure 4 Selecting the resource to be monitored
   

3. Select the static threshold template you have created.
   Figure 5 Selecting the static threshold template
   

4. Click Submit. As shown in the following figure, a multi-resource static threshold rule is created. Click to monitor the same metric of multiple resources.

   In the displayed host list, if the CPU usage of a host exceeds 85%, a threshold alarm is generated on the Alarm List page. You can choose Alarm Center > Alarm List in the navigation pane and view the alarm. If any host meets the preset notification policy, an email or SMS message will be sent.

   Figure 6 Creating a static threshold rule
   

Creating Multi-Resource Threshold Rules

1. Log in to the AOM console. In the navigation pane, choose Alarm Center > Threshold Rules.
2. On the Rule List tab page, click Create Default Threshold.

   AOM will automatically create six static threshold templates. You can click the Static Threshold Template tab to view the templates. For details, see Creating Default Static Threshold Templates. In addition, AOM will automatically create six default multi-resource threshold rules based on these templates. The monitored objects are all hosts or services, as shown in Figure 6. For example, click next to [node:default-static-rule] CPU Usage to monitor the CPU usage of all hosts.

   If you add hosts or services later, AOM automatically applies the rules to them.

   Figure 7 Creating default multi-resource threshold rules
   

   Table 1 Description of default multi-resource threshold rules

   Rule/Template	Resource	Metric	Default Configuration
   Rule: [node: default-static-rule] CPU Usage Template: [node: default-static-template] CPU Usage	Host	CPU usage	Statistic Method: Average; Threshold Condition: > 90%; Consecutive Periods: 3; Statistical Cycle: 1 minute; Alarm Severity: Major; Send Notification: No
   Rule: [node: default-static-rule] Physical Memory Usage Template: [node: default-static-template] Physical Memory Usage		Physical memory usage
   Rule: [node: default-static-rule] Node Status Template: [node: default-static-template] Node Status		Host status	Statistic Method: Average; Threshold Condition: > 0; Consecutive Periods: 1; Statistical Cycle: 1 minute; Alarm Severity: Major; Send Notification: No
   Rule: [service: default-static-rule] CPU Usage Template: [service: default-static-template] CPU Usage	Component	CPU usage	Statistic Method: Average; Threshold Condition: > 90%; Consecutive Periods: 3; Statistical Cycle: 1 minute; Alarm Severity: Major; Send Notification: No
   Rule: [service: default-static-rule] Physical Memory Usage Template: [service: default-static-template] Physical Memory Usage		Physical memory usage
   Rule: [service: default-static-rule] Status Template: [service: default-static-template] Status		Component status	Statistic Method: Average; Threshold Condition: > 0; Consecutive Periods: 1; Statistical Cycle: 1 minute; Alarm Severity: Major; Send Notification: No

More Operations

After creating threshold rules, perform the operations listed in Table 2 if needed.