Help Center> Cloud Eye> User Guide> Event Monitoring> Creating an Alarm Rule to Monitor an Event
Updated on 2024-03-15 GMT+08:00

Creating an Alarm Rule to Monitor an Event

Scenarios

This topic describes how to create an alarm rule to monitor an event.

Procedure

  1. Log in to the management console.
  2. Click Service List in the upper left corner, and select Cloud Eye.
  3. In the navigation pane on the left, choose Event Monitoring.
  4. On the event list page, click Create Alarm Rule in the upper right corner.
  5. On the Create Alarm Rule page, configure the parameters.
    1. Set the alarm rule name and description.
      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.
      Figure 1 Configuring parameters
      Table 2 Parameter description

      Parameter

      Description

      Alarm Type

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

      Event Type

      Specifies the event type, which can be System event or Custom event.

      Event Source

      Specifies the service the event is generated for.

      Example value: Elastic Cloud Server

      For a custom event, set Event Source to the value of event_source.

      Monitoring Scope

      Specifies the monitoring scope for event monitoring.

      Example value: All resources

      Method

      Specifies the means you use to create the alarm rule.

      Event Name

      Specifies the instantaneous operations users performed on resources, such as login and logout.

      For events supported by event monitoring, see Events Supported by Event Monitoring.

      Example value: Delete ECS

      Trigger Mode

      You can select immediate trigger or accumulative trigger based on the operation severity.

      Example value: Immediate trigger

      Alarm Policy

      Specifies the policy for triggering an alarm.

      For example, an alarm is triggered if the event occurred for three consecutive periods of 5 minutes.

      NOTE:

      This parameter is mandatory when Triggering Mode is set to Accumulative Trigger.

      Alarm Severity

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

      Example value: Major

    3. Configure the alarm notification.
      Figure 2 Alarm notification
      Table 3 Parameter description

      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 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 first and add subscriptions to it. For details, see Creating a Topic and Adding Subscriptions.

      Validity Period

      Cloud Eye sends notifications only within the validity period 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 trigger of alarm notifications.

    4. Configure the Enterprise Project and Tag.
      Figure 3 Advanced Settings
      Table 4 Name and Description

      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 about how to create an enterprise project, see Creating an Enterprise Project.

      Tag

      A tag consists of a key-value pair. Tags can be used to categorize and search for your resources. You can create tags using TMS. For details, see Creating Predefined Tags.

      If your organization has configured tag policies for Cloud Eye, follow the policies when configure Tag for an alarm rule. If the tag configured does not comply with the tag policies, alarm rules may fail to be created. In this case, contact your administrator to learn more about the tag policies.

      • A key can contain up to 128 characters, and a value can contain up to 225 characters.
      • You can create up to 20 tags.
    5. Click Create.