Alibaba Cloud PolarDB MySQL¶

Alibaba Cloud PolarDB MySQL Metrics display, including CPU usage, memory hit rate, network traffic, connection count, QPS, TPS, read-only node delay, etc.

Configuration¶

Install Func¶

It is recommended to activate Guance integration - extension - DataFlux Func (Automata): all prerequisites are automatically installed. Please continue with the script installation.

If you deploy Func by yourself, refer to Self-deployed Func

GSE version deployment is recommended.

Install Script¶

Note: Prepare an Alibaba Cloud AK that meets the requirements in advance (for simplicity, you can directly grant global read-only permission ReadOnlyAccess).

To synchronize Alibaba Cloud PolarDB MySQL monitoring data, we install the corresponding collection script: "Guance Integration (Alibaba Cloud-PolarDB Collection)" (ID: guance_aliyun_polardb)

After clicking 【Install】, input the corresponding parameters: Alibaba Cloud AK, Alibaba Cloud account name.

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

Once activated, you can see the corresponding automatic trigger configuration under "Manage / Automatic Trigger Configuration". Click 【Execute】to immediately execute it once without waiting for the scheduled time. After a short wait, you can view the execution task records and corresponding logs.

If you want to collect the corresponding logs, you need to enable the corresponding log collection script. If you want to collect bills, you need to enable the cloud bill collection script.

We default to collecting some configurations, details see the metrics section

Configure Custom Cloud Object Metrics

Verification¶

1. Confirm in "Manage/Automatic Trigger Configuration" whether the corresponding task has an automatic trigger configuration. You can also check the corresponding task records and logs for any anomalies.
2. In the Guance platform, check if there are asset information under "Infrastructure / Custom".
3. In the Guance platform, check if there are corresponding monitoring data under "Metrics".

Metrics¶

After configuring Alibaba Cloud - Cloud Monitor, the default measurement set is as follows. You can collect more metrics through configuration Alibaba Cloud Cloud Monitor Metrics Details

Objects¶

Collected Alibaba Cloud PolarDB MySQL object data structure, which can be seen in "Infrastructure - Custom" objects data

{
  "measurement": "aliyun_polardb",
  "tags": {
    "name"                : "pc-xxxx",
    "RegionId"            : "cn-hangzhou",
    "VpcId"               : "vpc-xxxx",
    "DBNodeNumber"        : "2",
    "PayType"             : "Postpaid",
    "DBType"              : "MySQL",
    "LockMode"            : "Unlock",
    "DBVersion"           : "8.0",
    "DBClusterId"         : "pc-xxxx",
    "DBClusterNetworkType": "VPC",
    "ZoneId"              : "cn-hangzhou-i",
    "Engine"              : "POLARDB",
    "Category"            : "Normal",
    "DBClusterDescription": "pc-xxxx",
    "DBNodeClass"         : "polar.mysql.x4.medium"
  },
  "fields": {
    "DBNodes"   : "{JSON Data of Node List}",
    "Database"  : "[JSON Data of Database Details]",
    "ExpireTime": "",
    "CreateTime": "2022-06-17T06:07:19Z",
    "message"   : "{Instance JSON Data}"
  }
}

Logs¶

Slow Query Statistics¶

Prerequisites¶

Note: The code execution of this script depends on the collection of PolarDB instance objects. If the custom object collection for PolarDB is not configured, the slow log script cannot collect slow log data.

Install Script¶

Based on the previous setup, you need to install another script corresponding to the PolarDB Slow Query Statistics Log Collection

In "Manage / Script Market", click and install the corresponding script package:

• "Guance Integration (Alibaba Cloud - PolarDB Slow Query Statistics Log Collection)" (ID: guance_aliyun_polardb_slowlog)

After the data is synchronized normally, you can view the data in the "Logs" section of Guance.

The reported data example is as follows:

{
  "measurement": "aliyun_polardb_slowlog",
  "tags": {
    "DBName"  : "PolarDB_MySQL",
    "DBNodeId": "pi-***************"
  },
  "fields": {
    "CreateTime"          : "2023-05-22Z",
    "MaxExecutionTime"    : 60,
    "MaxLockTime"         : 1,
    "ParseMaxRowCount"    : 1,
    "ParseTotalRowCounts" : 2,
    "ReturnMaxRowCount"   : 3,
    "ReturnTotalRowCounts": 1,
    "SQLHASH"             : "U2FsdGVkxxxx",
    "SQLText"             : "select id,name from tb_table",
    "TotalExecutionCounts": 2,
    "TotalExecutionTimes" : 2,
    "TotalLockTimes"      : 1,
    "message"             : "{Log JSON Data}"
  }
}

Descriptions of some parameters are as follows:

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

Note: fields.message is a JSON serialized string

Slow Query Details¶

Prerequisites¶

Note: The code execution of this script depends on the collection of PolarDB instance objects. If the custom object collection for PolarDB is not configured, the slow log script cannot collect slow log data.

Install Script¶

Based on the previous setup, you need to install another script corresponding to the PolarDB Slow Query Detail Log Collection

In "Manage / Script Market", click and install the corresponding script package:

• "Guance Integration (Alibaba Cloud - PolarDB Slow Query Detail Log Collection)" (ID: guance_aliyun_polardb_slowlog_record)

After the data is synchronized normally, you can view the data in the "Logs" section of Guance.

Configuration Cloud Database PolarDB Slow Query Details

The reported data example is as follows:

{
  "measurement": "aliyun_polardb_slowlog_record",
  "tags": {
    "DBName"     : "PolarDB_MySQL",
    "DBNodeId"   : "pi-***************",
    "HostAddress": "testdb[testdb] @ [100.**.**.242]"
  },
  "fields": {
    "SQLText"           : "select id,name from tb_table",
    "ExecutionStartTime": "2021-04-07T03:47Z",
    "QueryTimes"        : 20,
    "ReturnRowCounts"   : 0,
    "ParseRowCounts"    : 0,
    "LockTimes"         : 0,
    "QueryTimeMS"       : 100,
    "message"           : "{Log JSON Data}"
  }
}

Descriptions of some parameters are as follows:

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

Note: fields.message is a JSON serialized string