youjiageng1/doc-exports
1
0
Fork 0
forked from laiweijian4/doc-exports
Code Pull Requests Activity
doc-exports/docs/gaussdb_mysql/umn/gaussdb_03_0087.html
Wang , Deng Ke e944469104 gaussdb UMN 20221230 version 
Reviewed-by: Hasko, Vladimir <vladimir.hasko@t-systems.com>
Co-authored-by: Wang , Deng Ke <wangdengke2@huawei.com>
Co-committed-by: Wang , Deng Ke <wangdengke2@huawei.com>
2023-08-13 18:46:36 +00:00

4.8 KiB
Raw Blame History

Setting Alarm Rules

Scenarios

You can set alarm rules for GaussDB(for MySQL) to customize the monitored objects and notification policies and stay aware of the GaussDB(for MySQL) operating status.

The GaussDB(for MySQL) alarm rules include alarm rule names, services, dimensions, monitored objects, metrics, alarm thresholds, monitoring period, and whether to send notifications.

Procedure

  1. Log in to the management console.
  2. Under Management & Deployment, click Cloud Eye.
  3. In the navigation pane on the left, choose Cloud Service Monitoring > GaussDB(for MySQL).
  4. Locate the DB instance for which you want to create an alarm rule and click on the left, and then click Create Alarm Rule in the Operation column.
  5. On the displayed page, set parameters as required.

    • Specify Name and Description.
    • Select Use template for Method. The template contains the following common metrics: CPU usage, memory usage, and storage space usage.
    • Click to enable alarm notification. The validity period is 24 hours by default. If the topics you require are not displayed in the drop-down list, click Create an SMN topic. Then, select Generated alarm and Cleared alarm for Trigger Condition.

      Cloud Eye sends notifications only within the validity period specified in the alarm rule.

  6. Click Create. The alarm rule is created.

    For operation details, see the Cloud Eye User Guide.

Parent topic: Monitoring