Creating an Alarm Rule to Monitor a Server

Procedure

1. Log in to the Cloud Eye console.

2. In the navigation pane, choose Server Monitoring > Elastic Cloud Server (or Bare Metal Server).
3. Locate the target ECS or BMS, and choose More > Create Alarm Rule in the Operation column.
4. On the Create Alarm Rule page, configure the parameters.
   1. Configure the alarm rule name, description, and associated enterprise project.

      Table 1 Parameter description

      Parameter	Description
      Name	Alarm rule name. The system generates a random name, which you can modify. The rule name cannot exceed 128 characters and can contain only letters, digits, underscores (_), and hyphens (-). Example value: alarm-b6al
      Description	Alarm rule description. The value can contain a maximum of 256 characters. This parameter is optional.

   2. Select resources and configure other parameters.

      Table 2 Parameter description

      Parameter	Description	Example Value
      Alarm Type	Alarm type that the alarm rule applies to. The default value is Metric.	Metric
      Cloud Product	Name of the monitored service. By default, it is the cloud service that the selected resource belongs to. For details about supported cloud products and their metrics, see Cloud Product Metrics.	Elastic Cloud Server - ECSs
      Resource Level	Resource level of the monitored object. When you create an alarm rule for a specified resource in Server Monitoring, the resource level is set to Cloud product by default.	Cloud product
      Monitoring Scope	Monitoring scope the alarm rule applies to. When you create an alarm rule for a specified resource in Server Monitoring, the monitoring scope is set to Specific resources by default.	Specific resources
      Monitored Object	You do not need to set the monitored object because it is the resource you selected.	N/A
      Method	Method for configuring an alarm policy. The options are as follows: Configure manually: You can create a custom alarm policy as needed. Associate template: If the same alarm rule needs to be configured for multiple groups of resources under the same cloud product, you can use an alarm template to simplify operations.	Create manually
      Template	Select the template to be imported. This parameter is mandatory when Method is set to Associate template. You can select a default alarm template or a custom template.	N/A
      Alarm Policy	If you select Configure manually for Method, you need to configure alarm policies. For example, an alarm is triggered if the average CPU usage of the monitored object is 80% or more for three consecutive 5-minute periods. Cloud Eye triggers an alarm every one hour again if the alarm persists. You can add up to 50 alarm policies for a single alarm rule. You can choose to send alarm notifications when any of the policies is met or when all policies are met. For details about alarm policy parameters, see Alarm Policies. For details about basic and OS monitoring metrics, see Cloud Product Metrics. NOTE: If the alarm is not cleared after it is generated, an alarm notification is sent, once every hour.	N/A

   3. Configure the alarm notification.

      Table 3 Alarm Notification parameters

      Parameter	Description
      Alarm Notification	Whether to send alarm notifications by SMS, emailFunctionGraph (function), FunctionGraph (Workflow), WeCom, DingTalk, Lark, WeLink or HTTP or HTTPS. This parameter is enabled by default.
      Notified By	Notification method. You can select Notification groups, or Topic subscriptions. Notification groups: You need to create notification recipients and add them to a notification group. Topic subscriptions: You can select a cloud account contact or a custom topic created in SMN. NOTE: Cloud Eye uses SMN for alarm notifications. If SMN has major delays, the alarm notifications may also be delayed.
      Notification Group	The notification group for receiving alarm notifications. For details, see Creating a Recipient and Notification Group.
      Recipient	Target recipient of alarm notifications. You can select the account contact or a topic name. This parameter is available only if Notified By is set to Topic subscriptions. If there is a display name of a topic, the format is Topic name (display name), and you can search for a topic by name or display name. If no display name is set for a topic, only the topic name will be displayed. Account contact: Enter the phone number and email address of the registered account. Topic: A topic is used to publish messages and subscribe to notifications. If the required topic is unavailable, create one and add subscriptions to it on the SMN console. For details, see Creating a Topic and Adding Subscriptions. For the HTTP/HTTPS messages, see Simple Message Notification User Guide.
      Validity Period	Cloud Eye sends notifications only within the notification window specified in the alarm rule. If Validity Period is set to 08:00-20:00, Cloud Eye sends notifications only from 08:00 to 20:00.
      Time Zone	Time zone for the alarm notification window. By default, it matches the time zone of the client server, but can be manually configured.
      Trigger Condition	Condition that will trigger an alarm notification. You can select Generated alarm (when an alarm is generated), Cleared alarm (when an alarm is cleared), or both.

   4. Configure parameters in Advanced Settings.
      Figure 1 Advanced Settings
      

      Table 4 Parameters of Advanced Settings

      Parameter	Description
      Enterprise Project	Enterprise project that the alarm rule belongs to. Only users with the enterprise project permissions can manage the alarm rule. To create an enterprise project, see Creating an Enterprise Project.
      Tag	A tag is a key-value pair. Tags identify cloud resources so that you can easily categorize and search for your resources. You are advised to create predefined tags in TMS. For details, see Creating Predefined Tags. If you have configured tag policies for Cloud Eye, add tags to alarm rules based on the tag policies. If you add a tag that does not comply with the tag policies, alarm rules may fail to be created. Contact your administrator to learn more about tag policies. A key can contain a maximum of 128 characters, and a value can contain a maximum of 225 characters. A maximum of 20 tags can be added.

   5. Click Create.