Tencent Cloud Redis¶

Tencent Cloud Redis Metrics Display, including connections, requests, latency, slow queries, etc.

Configuration¶

Install Func¶

It is recommended to enable TrueWatch Integration - Expansion - Managed Func: All prerequisites are automatically installed. Please continue with the script installation.

If you deploy Func on your own, refer to Self-deployed Func

Installation Script¶

Note: Please prepare a Tencent Cloud AK that meets the requirements in advance (for simplicity, you can directly grant global read-only permissions ReadOnlyAccess).

To synchronize monitoring data for Tencent Cloud - Redis, we install the corresponding collection script: "TrueWatch Integration (Tencent Cloud - Redis Collection)" (ID: truewatch_tencentcloud_redis)

After clicking [Install], input the corresponding parameters: Tencent Cloud AK, Tencent Cloud account name.

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

In addition, you can see the corresponding automatic trigger configuration in "Manage / Automatic Trigger Configuration". Click [Execute]to immediately execute it once without waiting for the scheduled time. After a short while, you can view the execution task records and corresponding logs.

We default collect some configurations, for more details see the metrics section Customize cloud object metrics

Verification¶

1. In "Manage / Automatic Trigger Configuration", confirm whether the corresponding task has an automatic trigger configuration, and at the same time, you can check the corresponding task records and logs to see if there are any abnormalities.
2. On the TrueWatch platform, under "Infrastructure / Custom", check if there is asset information.
3. On the TrueWatch platform, under "Metrics", check if there are corresponding monitoring data.

Metrics¶

After configuring Tencent Cloud - Redis, the default metric sets are as follows. More metrics can be collected through configuration Tencent Cloud Monitoring Metrics Details

Redis Instance Monitoring¶

Overview of Parameters Corresponding to Each Dimension¶

Input Parameter Explanation¶

To query Redis instance monitoring data, input parameters are as follows: &Namespace=QCE/REDIS_MEM &Instances.N.Dimensions.0.Name=instanceid &Instances.N.Dimensions.0.Value=Instance ID

To query Proxy node monitoring data, input parameters are as follows: &Namespace=QCE/REDIS_MEM &Instances.N.Dimensions.0.Name=instanceid &Instances.N.Dimensions.0.Value=Instance ID &Instances.N.Dimensions.1.Name=pnodeid &Instances.N.Dimensions.1.Value=Proxy node ID

To query Redis node monitoring data, input parameters are as follows: &Namespace=QCE/REDIS_MEM &Instances.N.Dimensions.0.Name=instanceid &Instances.N.Dimensions.0.Value=Instance ID &Instances.N.Dimensions.1.Name=rnodeid &Instances.N.Dimensions.1.Value=Redis node ID

To query Redis latency metrics (command dimension) monitoring data, input parameters are as follows: &Namespace=QCE/REDIS_MEM &Instances.N.Dimensions.0.Name=instanceid &Instances.N.Dimensions.0.Value=Instance ID &Instances.N.Dimensions.1.Name=command &Instances.N.Dimensions.1.Value=Specific command word

Object¶

The structure of collected Tencent Cloud Redis object data can be viewed in "Infrastructure - Custom"

{
  "measurement": "tencentcloud_redis",
  "tags": {
    "name": "crs-xxxx",
    "BillingMode": "0",
    "Engine": "Redis",
    "InstanceId": "crs-xxxx",
    "InstanceName": "solution",
    "Port": "6379",
    "ProductType": "standalone",
    "ProjectId": "0",
    "RegionId": "ap-shanghai",
    "Status": "2",
    "Type": "6",
    "WanIp": "172.x.x.x",
    "ZoneId": "200002"
  },
  "fields": {
    "ClientLimits": "10000",
    "Createtime": "2022-07-14 13:54:14",
    "DeadlineTime": "0000-00-00 00:00:00",
    "InstanceNodeInfo": "{Instance node information}",
    "InstanceTitle": "Running",
    "Size": 1024,
    "message": "{Instance JSON data}"
  }
}

Logs¶

Slow Query Statistics¶

Prerequisites for Slow Query Statistics¶

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

Slow Query Statistics Installation Script¶

Based on the previous steps, another corresponding script needs to be installed for RDS Slow Query Statistics Log Collection

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

• "TrueWatch Integration (Tencent Cloud - Redis Slow Query Log Collection)" (ID: truewatch_tencentcloud_redis_slowlog)

After data synchronization is normal, you can view the data in the "Logs" section of TrueWatch.

An example of the reported data is as follows:

{
  "measurement": "tencentcloud_redis_slow_log",
  "tags": {
    "BillingMode": "0",
    "Client": "",
    "Engine": "Redis",
    "InstanceId": "crs-rha4zlon",
    "InstanceName": "crs-rha4zlon",
    "Node": "6d5d8cc6fxxxx",
    "Port": "6379",
    "ProductType": "standalone",
    "ProjectId": "0",
    "RegionId": "ap-shanghai",
    "Status": "2",
    "Type": "8",
    "WanIp": "172.17.0.9",
    "ZoneId": "200002",
    "name": "crs-xxxx"
  },
  "fields": {
    "Command": "config",
    "CommandLine": "config get whitelist-ips",
    "Duration": 1,
    "ExecuteTime": "2022-07-22 18:00:28",
    "message": "{Instance JSON data}"
  }
}

Part of the parameter explanation is as follows:

Note: Fields in tags and fields may change with subsequent updates. Note 1: The value of tags.name is the instance ID, which serves as a unique identifier. Note 2: fields.message is a JSON serialized string.