Huawei Cloud AS¶
The core performance metrics of Huawei Cloud AS (Auto Scaling) include CPU utilization, memory usage, disk I/O, network throughput, and system load, which are key indicators for evaluating and optimizing the performance of the auto-scaling system.
Configuration¶
Install Func¶
It is recommended to activate the Guance integration - extension - DataFlux Func (Automata): all prerequisites are automatically installed, please proceed with the script installation.
If you deploy Func manually, refer to Manual Func Deployment
Install Script¶
Note: Please prepare the Huawei Cloud AK that meets the requirements in advance (for simplicity, you can directly grant the global read-only permission
Tenant Guest)
Automata Activation Script¶
- Log in to the Guance console
- Click the 【Integration】 menu, select 【Cloud Account Management】
- Click 【Add Cloud Account】, select 【Huawei Cloud】, and fill in the required information on the interface. If you have already configured the cloud account information before, ignore this step
- Click 【Test】, and click 【Save】 after the test is successful. If the test fails, please check if the relevant configuration information is correct and test again
- Click 【Cloud Account Management】 list to see the added cloud account, click the corresponding cloud account to enter the details page
- Click the 【Integration】 button on the cloud account details page, find
Huawei Cloud ASunder theNot Installedlist, and click the 【Install】 button to pop up the installation interface and install it.
Manual Activation Script¶
-
Log in to the Func console, click 【Script Market】, enter the Guance script market, and search for
integration_huaweicloud_as -
Click 【Install】, and enter the corresponding parameters: Huawei Cloud AK, SK, and account name
-
Click 【Deploy Startup Script】, the system will automatically create the
Startupscript set and automatically configure the corresponding startup scripts -
After activation, you can see the corresponding automatic trigger configuration in 「Manage / Automatic Trigger Configuration」. Click 【Execute】 to execute it immediately without waiting for the scheduled time. After a while, you can check the execution task records and corresponding logs
Verification¶
- In 「Manage / Automatic Trigger Configuration」, confirm whether the corresponding task has the corresponding automatic trigger configuration, and check the corresponding task records and logs to see if there are any exceptions
- In Guance, check if there is asset information in 「Infrastructure / Custom」
- In Guance, check if there is corresponding monitoring data in 「Metrics」
Metrics¶
After configuring HUAWEI SYS.AS, the default measurement is as follows. You can collect more metrics by configuring Huawei Cloud Cloud Monitoring Metrics Details
| Metric Name | Description | Unit | Dimension |
|---|---|---|---|
| cpu_util | This metric is used to count the CPU utilization of the auto-scaling group | % | AutoScalingGroup |
| instance_num | This metric is used to count the number of available cloud servers in the auto-scaling group | count | AutoScalingGroup |
| disk_read_bytes_rate | This metric is used to count the amount of data read from the auto-scaling group per second | Byte/s | AutoScalingGroup |
| disk_write_bytes_rate | This metric is used to count the amount of data written to the auto-scaling group per second | Byte/s | AutoScalingGroup |
| mem_usedPercent | This metric is used to count the (Agent) memory usage of the auto-scaling group | % | AutoScalingGroup |
| cpu_usage | This metric is used to count the (Agent) CPU usage of the auto-scaling group | % | AutoScalingGroup |
Objects¶
The collected HUAWEI SYS.AS object data structure can be seen in 「Infrastructure-Custom」
{
"measurement": "huaweicloud_as",
"tags": {
"name" : "c4dec56f-96b0-40f4-b47d-ab0cdc47e908",
"scaling_configuration_id" : "c4dec56f-96b0-40f4-b47d-ab0cdc47e908",
"scaling_configuration_name" : "as-config-cdec",
"scaling_group_id" : "da854ab8-bd88-4757-a35a-135c7c3d526d"
},
"fields": {
"created_time" : "2022-06-21T06:17:27+0000",
"instance_config" : "{instance configuration information}",
"message" : "{instance JSON data}"
}
}
Note: The fields in
tagsandfieldsmay change with subsequent updatesTip 1: The value of
tags.nameis the instance ID, used as a unique identifierTip 2:
fields.message,fields.billing,fields.bind_rules,fields.message,fields.resourcesare all JSON serialized strings