Help Center> Cloud Eye> User Guide> Server Monitoring> Creating an Alarm Rule to Monitor a Server
Updated on 2024-01-18 GMT+08:00

Creating an Alarm Rule to Monitor a Server

Scenarios

This topic describes how to create an alarm rule to monitor an ECS or BMS.

Procedure

  1. Log in to the management console.
  2. In the upper left corner, select a region and project.
  3. Click Service List in the upper left corner, and select Cloud Eye.
  4. In the navigation pane on the left, choose Server Monitoring.
  5. Locate the target ECS or BMS. In the Operation column, choose More > Create Alarm Rule.
  6. On the Create Alarm Rule page, follow the prompts to configure parameters.
    1. Set the alarm rule name, description, and associated enterprise project.
      Table 1 Parameter description

      Parameter

      Description

      Name

      Specifies the alarm rule name. The system generates a random name, which you can modify.

      Description

      (Optional) Provides supplementary information about the alarm rule.

    2. Select a monitored object and configure alarm content parameters.
      Table 2 Parameter description

      Parameter

      Description

      Example Value

      Alarm Type

      Specifies the alarm type to which the alarm rule applies. The value can be Metric or Event.

      Metric

      Resource Type

      Specifies the type of the resource the alarm rule is created for.

      Elastic Cloud Server

      Dimension

      Specifies the metric dimension of the selected resource type.

      ECSs

      Monitoring Scope

      Specifies the monitoring scope the alarm rule applies to.

      Specific resources

      Monitored Object

      You do not need to set the monitored object because it is the current ECS.

      N/A

      Method

      There are three options: Associate template, Use existing template, and Configure manually.

      NOTE:

      After an associated template is modified, the policies contained in this alarm rule to be created will be modified accordingly.

      Create manually

      Template

      Specifies the template to be used.

      You can select a default alarm template or a custom template.

      N/A

      Alarm Policy

      Specifies the policy for triggering an alarm.

      For example, an alarm is triggered if the average CPU usage of the ECS is 80% or more for three consecutive 5-minute periods. Cloud Eye triggers an alarm every one hour again if the alarm persists.

      For details about basic and OS monitoring metrics, see Services Interconnected with Cloud Eye.

      NOTE:
      • That is, if the alarm is not cleared after it is generated, an alarm notification is sent every hour.
      • A maximum of 50 alarm policies can be added to an alarm rule. If any one of these alarm policies is met, an alarm is triggered.

      N/A

      Alarm Severity

      Specifies the alarm severity, which can be Critical, Major, Minor, or Informational.

      Major

    3. Configure the alarm notification.
      Table 3 Alarm Notification parameters

      Parameter

      Description

      Alarm Notification

      Specifies whether to notify users when alarms are triggered. Notifications can be sent by email, text message, or HTTP/HTTPS message.

      Notification Object

      Specifies the object to which alarm notifications will be sent. You can select the account contact or a topic.

      • Account contact is the mobile 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 HTTP/HTTPS Messages.

      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 within 08:00–20:00.

      Trigger Condition

      Specifies the condition for triggering the alarm notification. You can select Generated alarm (when an alarm is generated), Cleared alarm (when an alarm is cleared), or both.

    4. Configure the enterprise project and tag.
      Figure 1 Advanced Settings
      Table 4 Parameters of Advanced Settings

      Parameter

      Description

      Enterprise Project

      Specifies the enterprise project that the alarm rule belongs to. Only users who have all permissions for the enterprise project can view and manage the alarm rule. For details, 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.

After the alarm rule is created, if the metric reaches the specified threshold, Cloud Eye immediately informs you that an exception has occurred.