Creating an Alarm Rule to Monitor a Server

Prerequisites

• Before creating an alarm rule for Agent metrics, ensure that Agent has been installed on the server. For details, see Installing the Agent.
• Before creating an alarm rule for process monitoring metrics, ensure that you have added custom processes for monitoring. For details, see Adding Process Monitoring.

Billing

Alarm notifications sent by SMN will be billed based on their frequency and message length. For details, see Product Pricing Details.

Creating an Alarm Rule for a Specified Server

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 displayed page, the monitored object is the selected resource by default. Configure parameters as prompted.
   1. Enter an alarm rule name.

      The system generates a random name, which you can modify. The name cannot exceed 128 characters and can contain only letters, digits, underscores (_), and hyphens (-).

   2. Configure alarm policy parameters as prompted. For details about alarm policies, see Alarm Policy Parameters.
   3. Configure alarm notifications.
      Figure 1 Configuring alarm notifications
      

      Table 1 Parameters for configuring alarm notifications

      Parameter	Description
      Alarm Notifications	Whether to send alarm notifications by SMS, email, FunctionGraph (function), FunctionGraph (Workflow), WeCom, DingTalk, Lark, WeLink, HTTP, or HTTPS. This parameter is enabled by default.
      Notified By	Notification method. You can select Notification policies, Contact groups, or Topic subscriptions. Notification policies: If several O&M owners handle service maintenance, you can set up different notification scopes in a notification policy to alert specific owners by alarm severity or at a specified schedule. For details, see Creating a Notification Policy. Contact groups: Cloud Eye provides alarm notification capabilities. Select this option if you do not need to send alarm notifications by severity or schedule. To send alarm notifications to a group of contacts, you can create a contact group and add contacts to it in Cloud Eye for easier management. For details, see Creating a Contact/Contact Group. Topic subscriptions: If the current region does not support alarm notifications or the recipients have been configured in SMN, you can select a topic created in SMN or your cloud account contact as required. For details, see Creating a Topic and Adding Subscriptions. NOTE: Cloud Eye uses SMN for alarm notifications. If SMN has major delays, the alarm notifications may also be delayed.
      Notification Window	Notification window during which Cloud Eye only sends notifications. If you set this parameter to 08:00 to 20:00, Cloud Eye only sends notifications within this period.
      Time Zone	Time zone for the alarm notification window. By default, it matches the time zone of the client browser, 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.
      Notification Template	This parameter is only available if you set Notified By to Contact groups or Topic subscriptions. You can select an existing template or create one to send alarm notifications. NOTE: Some cloud services do not support fields such as the resource name, enterprise project, resource tag, private IP address, and public IP address in the notification template. When you select a system template as the notification template, these fields will appear blank in the alarm notifications even if you have them configured.

   4. Configure parameters in Advanced Settings.
      Figure 2 Advanced settings
      

      Table 2 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. For details about how to create an enterprise project, see Creating an Enterprise Project.
      Tag	Each tag is a key-value pair. You can tag cloud resources to easily categorize and search for them. 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 up to 128 characters, and a value can contain up to 255 characters. You can create up to 20 tags.
      Description	(Optional) Alarm rule description. It can contain up to 256 characters.
      No-Data Processing	If Alarm Type is set to Metric, you can configure how to handle no-data alarms. You can choose to send an alarm, consider the alarm cleared, or take no action. Generate no-data alarms: If a metric configured in the alarm rule does not report data for three consecutive hours, an alarm record will be generated indicating insufficient data. Treated as cleared: If a metric configured in the alarm rule does not report data for three consecutive hours, the alarm record generated by the current alarm rule will be treated as cleared. No action: If a metric configured in the alarm rule does not report data for three consecutive hours, no alarm record indicating insufficient data will be generated, and the alarm record generated by the alarm rule will not be cleared. NOTE: Generally, if a cloud service metric does not report data for three consecutive hours, the data is considered insufficient. If the reporting period of a metric is longer than three hours and no monitoring data is reported for three consecutive periods, the data is also considered insufficient. In some regions, a switch is provided to determine whether to generate an alarm when no data is reported. By default, this switch is enabled. When enabled, an insufficient data alarm record will be generated if the configured metric reports no data for three consecutive hours.

   5. Click Create.

After the alarm rule is created, if a metric reaches the specified threshold, Cloud Eye immediately informs you of the exception through SMN.

Creating an Alarm Rule for a Specified Metric of a Server

1. Log in to the Cloud Eye console.

2. In the navigation pane, choose Server Monitoring > Elastic Cloud Server (or Bare Metal Server).
3. Click View Metric in the Operation column of the target ECS or BMS.
4. Click the OS Monitoring or Basic Monitoring tab as required.
5. In the upper right corner of the graph of the target metric, click .
6. On the displayed page, configure the alarm policies and notifications.

   For details about alarm notification parameters, see Table 1.

7. Click Create.

Creating an Alarm Rule for a Specified Process of a Server

1. Log in to the Cloud Eye console.

2. In the navigation pane, choose Alarm Management > Rule Settings.
   

   In some regions, the path is Alarm Management > Alarm Rules.

3. Click Create Alarm Rule in the upper right corner.
4. On the Create Alarm Rule page, configure the basic information about the alarm rule. For details, see Basic Parameters of an Alarm Rule.

   The following uses an ECS as an example to describe how to set alarm content parameters. The procedure for BMSs is similar.

   • Alarm Type: Metric
   • Cloud Product: Elastic Cloud Server - ECSs
   • Resource Level: Select Specific dimension and then select the dimension name.
     • To configure an alarm rule for a specified number of processes, select ECSs - Process.
     • To configure an alarm rule for the CPU usage, memory usage, or number of opened files of a specified process, select ECSs - Process - ProcessIDs.
   • Monitoring Scope: Select Specific resources.
   • Instance: Click Select Specific Resources. In the displayed list, click next to the target resource name, and select the target process.
5. Configure an alarm policy. You can select an alarm template that contains the selected dimension metrics or customize an alarm policy. For details about alarm policy parameters, see Alarm Policy Parameters.
6. Configure alarm notification parameters. For details, see Table 1.
7. Click Create.

Helpful Links

When a metric reaches the threshold set for an alarm rule, you can check the monitoring details on the Alarm Records page. For details, see Viewing Alarm Records.