Viewing GaussDB(DWS) Cluster Monitoring Information on Cloud Eye

Function

This section describes how to check cluster metrics on Cloud Eye. By monitoring cluster running metrics, you can identify the time when the database cluster is abnormal and analyze potential activity problems based on the database logs, improving database performance. This section describes the metrics that can be monitored by Cloud Eye as well as their namespaces and dimensions. You can use the management console or APIs provided by Cloud Eye to query the monitoring metrics and alarms generated by GaussDB(DWS).

Namespace

SYS.DWS

Cluster Monitoring Metrics

With the GaussDB(DWS) monitoring metrics provided by Cloud Eye, you can obtain information about the cluster running status and performance. This information will provide a better understanding of the node-level information.

Table 1 describes GaussDB(DWS) monitoring metrics.

Dimensions

Cluster and Node Monitoring Information

1. Log in to the GaussDB(DWS) console and choose Clusters > Dedicated Clusters.
2. View the cluster information. In the cluster list, click View Metric in the Operation column where a specific cluster resides. The Cloud Eye management console is displayed. By default, the cluster monitoring information on the Cloud Eye management console is displayed.

   Additionally, you can specify a specific monitoring metric and the time range to view the performance curve.

3. View the node information. Click to return to the Cloud Eye management console. On the Data Warehouse Nodes tab page in the right pane, you can view metrics of each node in the cluster.

   Additionally, you can specify a specific monitoring metric and the time range to view the performance curve.

   Cloud Eye also supports the ability to compare the monitoring metrics of multiple nodes. For details, see Comparing the Monitoring Metrics of Multiple Nodes.

Comparing the Monitoring Metrics of Multiple Nodes

1. In the navigation pane of the Cloud Eye management console, choose Dashboards > My Dashboards. Click the name of the dashboard for which you want to add a graph. On the My Dashboards page that is displayed, click Add Graph.
2. On the Add Graph page, you can select Line Chart or Bar Chart to display the graph. After confirming that the information is correct, click OK.

   For example, select Line Chart and One View for Multiple Metrics to compare the CPU usage of three GaussDB(DWS) nodes. The following table describes the parameters.

   

   Table 2 Configuration example

   Parameter	Example Value
   Resource Type	DWS
   Dimension	Data Warehouse Node
   Monitored Object	dws-demo-dws-cn-cn-2-1 dws-demo-dws-cn-cn-1-1 dws-demo-dws-dn-1-1
   Metric	CPU Usage

3. Click OK.

   On the selected My Dashboards page, you can view the metric trend on the newly added monitoring graph. You can click the zoom in button to zoom in and view detailed metric comparison data.

Creating Alarm Rules

GaussDB(DWS) enables you to customize alarm rules for monitoring specific objects and notification policies, ensuring you stay informed about its running status in a timely manner.

A GaussDB(DWS) alarm rule includes the alarm rule name, monitored object, metric, threshold, monitoring interval, and whether to send a notification. This section describes how to set GaussDB(DWS) alarm rules.

1. Log in to the GaussDB(DWS) console.
2. In the navigation pane, choose Clusters > Dedicated Clusters.
3. Locate the row containing the target cluster, click View Metric in the Operation column to enter the Cloud Eye management console and view the GaussDB(DWS) monitoring information.

   The status of the target cluster must be Available. Otherwise, you cannot create alarm rules.

4. In the left navigation pane of the Cloud Eye management console, choose Alarm Management > Alarm Rules.
5. On the Alarm Rules page, click Create Alarm Rule in the upper right corner.
6. On the Create Alarm Rule page, set parameters as prompted.
   1. Configure the rule name and description.
   2. Configure the alarm parameters as prompted.

      Table 3 Configuring alarm parameters

      Parameter	Description	Example Value
      Resource Type	Name of the cloud service resource for which the alarm rule is configured.	Data Warehouse Service
      Dimension	Metric dimension of the alarm rule. You can select Data Warehouse Nodes or Data Warehouses.	Data Warehouse Node
      Monitoring Scope	Resource scope to which an alarm rule applies. Select Specific resources and select one or more monitoring objects. For GaussDB(DWS), select the cluster ID or node ID in the dialog box that is displayed.	Specific resources
      Trigger Rule	You can select an associated template, use an existing template or create a custom template as required.	Create manually
      Template	This parameter is valid only when Use template is selected. Select the template to be imported. If no alarm template is available, click Create Custom Template to create one that meets your requirements.	-
      Alarm Policy	This parameter is valid only when Create manually is selected. Set the policy that triggers an alarm. For example, trigger an alarm if the CPU usage equals to or is greater than 80% for 3 consecutive periods. Table 1 lists the GaussDB(DWS) monitoring metrics.	-
      Alarm Severity	Severity of an alarm. Valid values are Critical, Major, Minor, and Informational.	Major

   3. Configure the alarm notification parameters as prompted.

      Table 4 Configuring alarm notifications

      Parameter	Description	Example Value
      Alarm Notification	Whether to notify users when alarms are triggered. Notifications can be sent as emails or text messages, or HTTP/HTTPS requests sent to the servers. You can enable (recommended) or disable Alarm Notification.	Enable
      Validity Period	Cloud Eye sends notifications only within the validity period specified in the alarm rule. For example, if Validity Period is set to 00:00-8:00, Cloud Eye sends notifications only within 00:00-8:00.	-
      Notification Object	Name of the topic to which the alarm notification is sent. If you enable Alarm Notification, you need to select a topic. If no desired topics are available, create one first, whereupon the SMN service is invoked. For details about how to create a topic, see the Simple Message Notification User Guide. For details about how to create a topic, see the Simple Message Notification User Guide.	-
      Trigger Condition	Condition for triggering the alarm. You can select Generated alarm, Cleared alarm, or both.	-

   4. After the configuration is complete, click Next.

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

Transferring Data to OBS

Raw data of metrics is kept for two days on Cloud Eye. You can enable OBS and save the raw data to OBS so that it can be saved for a longer time.

For how to configure OBS storage transfer, see "Viewing Alarm History" > "Configuring OBS Data Storage" in the Cloud Eye User Guide.