Help Center/ GaussDB/ User Guide/ Monitoring and Alarming/ Creating Alarm Rules for a GaussDB Instance
Updated on 2025-08-11 GMT+08:00

Creating Alarm Rules for a GaussDB Instance

Scenarios

You can set alarm rules to customize the monitored objects and notification policies and to stay aware of the operating status.

The alarm rules include alarm rule names, resource type, dimensions, monitored objects, metrics, alarm thresholds, monitoring period, and whether to send notifications.

Procedure

  1. Log in to the management console.
  2. Under Management & Governance of the service list, click Cloud Eye.
  3. In the navigation pane on the left, choose Cloud Service Monitoring.
  4. Click GaussDB in the list.
  5. Locate the instance for which you want to create an alarm rule, click More in the Operation column, and choose Create Alarm Rule.
  6. On the displayed page, set parameters as required.

    Table 1 Alarm rule information

    Parameter

    Description

    Name

    Alarm rule name. The system generates a random name, and you can change it if needed. The value can contain only letters, digits, underscores (_), and hyphens (-), and cannot exceed 128 characters.

    Description

    Description of the alarm rule. The value can contain a maximum of 256 characters. This parameter is optional.

    Method

    Mode for configuring an alarm policy. You can select Associate template or Configure manually.

    • Configure manually: You can create a custom alarm policy as needed.
    • Associate template: If the same alarm rule needs to be configured for multiple GaussDB instances, you can use an alarm template to simplify operation.

    Template

    This parameter is only available if you select Associate template for Method.

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

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

    Alarm Policy

    This parameter is only available if you select Configure manually for Method.

    An alarm is triggered when the metric configured for this alarm reaches the preset threshold in consecutive periods. For example, an alarm is triggered if the average CPU usage is 80% or higher for three consecutive 5-minute periods.

    A maximum of 50 alarm policies can be added to an alarm rule. If any of these alarm policies is met, an alarm will be triggered.

    Table 2 Alarm notification

    Parameter

    Description

    Alarm Notification

    Specifies whether to notify users when alarms are triggered. Notifications can be sent by email or text messages, or through HTTP/HTTPS requests to servers. This function is enabled by default.

    Notification Recipient

    The following three options are available:

    • Notification policies: Flexible alarm notifications by severity and more notification channels are provided.
    • Notification group: Configure notification templates on the Cloud Eye console.
    • Topic subscription: Configure notification templates on the Simple Message Notification (SMN) console.

    Notification Policies

    This parameter is only available if you select Notification policies for Notification Recipient. Select one or more notification policies. You can specify the notification group, window, template, and other parameters in a notification policy.

    For how to create a notification policy, see Creating, Modifying, or Deleting a Notification Policy.

    Notification Group

    This parameter is only available if you select Notification group for Notification Recipient. Select the notification groups to which alarm notifications will be sent.

    For details about how to create a notification group, see Creating a Notification Object and Notification Group.

    Notification Object

    This parameter is only available if you select Topic subscription for Notification Recipient. You can select the account contact or a topic as the object to which alarm notifications will be sent.

    • The account contact is the mobile phone number and email address of the registered account.
    • A topic is a specific event type for publishing messages or subscribing 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.

    Notification Template

    This parameter is only available if you select Notification group or Topic subscription for Notification Recipient. You can select an existing template or create a new one to send alarm notifications.

    Notification Window

    This parameter is only available if you select Notification group or Topic subscription for Notification Recipient.

    Cloud Eye sends notifications only within the notification window you specified.

    If Notification Window is set to 08:00-20:00, alarm notifications are sent only from 08:00 to 20:00.

    Trigger Condition

    This parameter is only available if you select Notification group or Topic subscription for Notification Recipient.

    You can select either Generated alarm or Cleared alarm, or both.

    Enterprise Project

    Enterprise project that the alarm rule belongs to. Only users who have the permissions of the enterprise project can view and manage this alarm rule.

    Tags

    Key-value pairs that you can use to easily categorize and search for cloud resources. You are advised to create predefined tags in Tag Management Service (TMS).

    If your organization has configured tag policies for Cloud Eye, you need to add tags to alarm rules based on tag policies. If a tag does not comply with the policies, an alarm rule may fail to be created. Contact your organization administrator to learn more about tag policies.

    • A key can contain up to 128 characters, and a value can contain up to 225 characters.
    • You can add up to 20 tags.

  7. Click Create. The alarm rule is created.

    For details about how to create alarm rules, see Creating an Alarm Rule.