This topic provides answers to some frequently asked questions about monitoring in AnalyticDB for MySQL.
If no edition is specified in a question, the question is applicable only to AnalyticDB for MySQL Data Warehouse Edition (V3.0) clusters.
How do I monitor the disk usage for an AnalyticDB for MySQL Data Warehouse Edition (V3.0) cluster in reserved mode for Cluster Edition?
To prevent the disk usage of your cluster from reaching the specified threshold, you can configure an alert rule to monitor the disk usage. When the disk usage reaches the threshold, an alert is immediately sent to the specified contacts. This helps you manage the disk storage as soon as issues arise to ensure the normal operation of your business.
Disk monitoring is not required for Data Lakehouse Edition (V3.0) clusters.
- Log on to the AnalyticDB for MySQL console.
- In the upper-left corner of the page, select a region.
- In the left-side navigation pane, click Clusters.
On the Data Warehouse Edition (V3.0) tab, find the cluster that you want to manage and click the cluster ID.
- In the left-side navigation pane, click Monitoring Information.
On the Monitoring Information page, click the Queries & Writes tab to view the disk usage.
In reserved mode, the disk usage is displayed as a percentage. In elastic mode, the used storage of disks where read/write nodes are located is displayed.
The maximum disk usage indicates the highest disk usage among all nodes in the cluster. If the value is greater than or equal to 90%, the disk is locked. We recommend that you pay special attention to this metric.
The used disk storage indicates the maximum disk storage that is used by a single read/write node. If the value of this metric is greater than or equal to 8 TB, data cannot be written to the cluster. We recommend that you pay special attention to this metric.
On the Monitoring Information page, click Alert Rule Settings to go to the CloudMonitor console.
- On the Alert Rules page, click Create Alert Rule.
- In the Create Alert Rule panel, configure the parameters that are described in the following table.
Parameter Description Product The name of the service for which you want to configure the alert rule. Select AnalyticDB for MySQL V3.0 - Data Warehouse Edition. Resource Range The resources to which you want to apply the alert rule. Valid values:
- All Resources: The alert rule applies to all clusters of the specified service. For example, you set the Resource Range parameter to All Resources for a rule that triggers an alert if the disk usage of an AnalyticDB for MySQL V3.0 cluster is greater than or equal to 80%. This alert rule applies to all AnalyticDB for MySQL V3.0 clusters within your Alibaba Cloud account. Each alert rule can be applied to up to 1,000 resources for a specified service. If your account contains more than 1,000 resources of the specified service, the system may not generate an alert regardless of whether the rule conditions are met. Before you configure the alert rule, we recommend that you sort resources into different application groups by service based on your business requirements.
- Application Group: The alert rule applies to all resources in the specified application group of the specified service.
- Instances: The alert rule applies to the specified instances of the specified service. For example, you set the Resource Range parameter to Instances for a rule that triggers an alert if the disk usage of a cluster is greater than or equal to 80%. An alert is triggered only if the disk usage of the specified cluster is greater than or equal to 80%.
Rule Description The content of the alert rule. This parameter specifies the conditions that trigger the alert. To specify the content of the alert rule, perform the following steps:
- Click Add Rule.
- In the Add Rule Description panel, configure the following parameters: Alert Rule, Metric Type, Metric, Threshold and Alert Level, and Chart Preview.
- Click OK.
Mute For The interval at which you want CloudMonitor to resend alert notifications if the alert is not cleared. Valid values: 5 Minutes, 15 Minutes, 30 Minutes, 60 Minutes, 3 Hours, 6 Hours, 12 Hours, and 24 Hours. An alert is triggered when the conditions of an alert rule are met. CloudMonitor does not resend an alert notification if the alert is triggered within the mute period. If the alert is not cleared after the mute period ends, CloudMonitor resends alert notifications. Effective Period The period of time during which the alert rule is in effect. The system monitors the metrics and generates alerts only during this period.Important Each contact can receive up to four alert notifications for disk usage every day. Alert Contact Group The alert contact group to which alert notifications are sent.
The alert notifications of the application group are sent to the alert contacts that belong to the specified alert contact groups. An alert contact group can contain one or more alert contacts. For information about how to create an alert contact and an alert contact group, see Create an alert contact or alert contact group.
Alert Callback The callback URL that can be accessed over the Internet. CloudMonitor sends a POST request to push an alert to the callback URL that you specified. Only HTTP requests are supported. For information about how to configure alert callbacks, see Use the alert callback feature to send notifications about threshold-triggered alerts.Note You can click Advanced Settings to configure this parameter. Auto Scaling If you turn on Auto Scaling, the specified scaling rule is enabled when an alert is triggered. In this case, configure the following parameters: Region, ESS Group, and ESS Rule.
Note You can click Advanced Settings to configure this parameter.
- For information about how to create a scaling group, see Manage scaling groups.
- For information about how to create a scaling rule, see Manage scaling rules.
Log Service If you turn on Log Service, the alert information is written to Log Service when an alert is triggered. In this case, configure the following parameters: Region, Project Name, and Logstore.
For information about how to create a project and a Logstore, see Getting Started.Note You can click Advanced Settings to configure this parameter.
Message Service - Topic If you turn on Message Service - topic, the alert information is written to the specified topic in Message Service (MNS) when an alert is triggered. In this case, select a region and a topic. For information about how to create a topic, see Create a topic. Method to handle alerts when no monitoring data is found The method that is used to handle alerts if no monitoring data exists. Valid values:
Note You can click Advanced Settings to configure this parameter.
- Do not do anything (default)
- Send alert notifications
- Treated as normal
Tag The tag that can be added to alert notifications. Each tag key is paired with a tag value. You can specify multiple pairs of tags.
- Click Confirm.
How do I view how much storage is used for hot data and cold data?
Log on to the AnalyticDB for MySQL console and go to the Monitoring Information page to view the amount of storage used for hot data and cold data.
How do I check the table size?
Log on to the AnalyticDB for MySQL console and go to the Monitoring Information page. Click the Table Information Statistics tab to view table statistics such as the table size.
Why is the used hot data storage displayed on the monitoring page greater than the used disk data storage?
An AnalyticDB for MySQL cluster contains multiple read/write nodes. The used disk data storage refers to the maximum disk storage that is used by a single read/write node. The used hot data storage refers to the total disk data storage that is used by all read/write nodes.
Why does the average CPU utilization increase on the monitoring page after I change my cluster from reserved mode to elastic mode?
When a C32 cluster in reserved mode is changed to elastic mode, the specifications of a single node decrease to 8 cores. By default, BUILD tasks occupy 3 cores. In this case, the average CPU utilization increases. If the increased average CPU utilization does not affect your business, ignore this change. If your business is affected, upgrade your cluster or submit a ticket. For more information about BUILD tasks, see BUILD.