Huawei Cloud Search Service CSS for Elasticsearch

Collect monitoring metrics for Huawei Cloud Search Service CSS for Elasticsearch

Configuration¶

Install Func¶

It is recommended to enable Guance Integration - Extensions - DataFlux Func (Automata): all prerequisites are automatically installed, please proceed with script installation.

If you need to deploy Func manually, refer to Manual Deployment of Func

Install Script¶

Note: Please prepare Huawei Cloud AK with appropriate permissions in advance (for simplicity, you can grant global read-only permission Tenant Guest)

Automata Version Installation Script¶

1. Log in to the Guance console
2. Click the 【Integration】 menu, select 【Cloud Account Management】
3. 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, you can skip this step
4. Click 【Test】, if the test is successful, click 【Save】. If the test fails, please check the relevant configuration information and test again
5. Click 【Cloud Account Management】, you can see the added cloud account in the list, click the corresponding cloud account to enter the details page
6. Click the 【Integration】 button on the cloud account details page, find Huawei Cloud Search Service CSS for Elasticsearch under the Not Installed list, and click the 【Install】 button to install.

Manual Installation Script¶

1. Log in to the Func console, click 【Script Market】, enter the Guance script market, search for integration_huaweicloud_css

2. Click 【Install】, then enter the corresponding parameters: Huawei Cloud AK, SK, and account name

3. Click 【Deploy Startup Script】, the system will automatically create the Startup script set and configure the corresponding startup script

4. After enabling, you can see the corresponding automatic trigger configuration in 「Management / Automatic Trigger Configuration」. Click 【Execute】 to execute immediately without waiting for the scheduled time. After a while, you can check the execution task records and corresponding logs

Verification¶

1. In 「Management / Automatic Trigger Configuration」, confirm whether the corresponding task has the corresponding automatic trigger configuration, and you can also check the corresponding task records and logs to see if there are any exceptions
2. In Guance, go to 「Infrastructure - Resource Catalog」 to check if there is asset information
3. In Guance, go to 「Metrics」 to check if there is corresponding monitoring data

Metrics¶

Configure Huawei Cloud CSS metrics, you can collect more metrics through configuration Huawei Cloud CSS Metrics Details

Instance Monitoring Metrics¶

Huawei Cloud Search Service CSS for Elasticsearch instance performance monitoring metrics, as shown in the table below. For more metrics, please refer to Table 1

Object¶

The data structure of the collected Huawei Cloud Search Service CSS for Elasticsearch object can be seen in 「Infrastructure - Resource Catalog」

{
  "measurement": "huaweicloud_css",
  "tags": {
    "RegionId"                   : "cn-north-4",
    "project_id"                 : "xxxxxxx",
    "enterpriseProjectId"        : "",
    "instance_id"                : "xxxxxxx-xxxxxxx-xxxxxxx-00001",
    "instance_name"              : "css-3384",
    "publicIp"                   : "xxxxx",
    "status"                     : "100",
    "endpoint"                   : "192.168.0.100:9200",
  },
  "fields": {
    "vpc_id"                     : "3dda7d4b-aec0-4838-a91a-28xxxxxxxx",
    "subnetId"                   : "xxxxx",
    "securityGroupId"            : "xxxxxxx",
    "datastore"                           : "{\"supportSecuritymode\": false, \"type\": \"elasticsearch\", \"version\": \"7.6.2\"}",
    "instances"                           : "[{\"azCode\": \"cn-east-3a\", \"id\": \"95f61e90-507b-48d4-8ac5-53dcefd155a3\", \"ip\": \"192.168.0.140\", \"name\": \"css-test-ess-esn-1-1\", \"specCode\": \"ess.spec-kc1.xlarge.2\", \"status\": \"200\", \"type\": \"ess\", \"volume\": {\"size\": 40, \"type\": \"HIGH\"}}]",
    "publicKibanaResp"                    : "xxxx",
    "elbWhiteList"                        : "xxxx",
    "updated"                             : "2023-06-27T07:35:29",
    "created"                             : "2023-06-27T07:35:29",
    "bandwidthSize"                       : "100",
    "actions"                             : "REBOOTING",
    "tags"                                : "xxxx",
    "period"                              : true, 
  }
}

Some parameter descriptions are as follows:

status (Cluster Status Value) Meaning:

actions (Current Actions of the Cluster) Meaning:

period Meaning:

Note: Fields in tags and fields may change with subsequent updates

Tip: The value of tags.instance_id is the cluster ID, which is used as a unique identifier