Skip to content

Tencent Cloud KeeWiDB¶

Tencent Cloud KeeWiDB Metrics Display, including connections, requests, caching, keys, slow queries, etc.

Configuration¶

Install Func¶

It is recommended to activate Guance Integration - Extensions - DataFlux Func (Automata): All prerequisites are automatically installed. Please proceed with the script installation.

If deploying Func manually, refer to Manual Func Deployment

Install Script¶

Note: Please prepare the required Tencent Cloud AK in advance (for simplicity, you can directly grant the global read-only permission ReadOnlyAccess).

To synchronize the monitoring data of Tencent Cloud KeeWiDB, we install the corresponding collection script: "Guance Integration (Tencent Cloud-KeeWiDB Collection)" (ID: integration_tencentcloud_keewidb).

Click [Install], then enter the relevant parameters: Tencent Cloud AK, Tencent Cloud account name.

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

Additionally, 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. Wait a moment, and you can view the execution task records and corresponding logs.

Verification¶

In "Manage / Automatic Trigger Configuration", confirm whether the corresponding task has the automatic trigger configuration, and check the corresponding task records and logs for any exceptions.
In Guance, check if asset information exists in "Infrastructure / Custom".
In Guance, check if there is corresponding monitoring data in "Metrics".

Metrics¶

After configuring Tencent Cloud KeeWiDB, the default Measurement is as follows. More Metrics can be collected through configuration Tencent Cloud Cloud Monitoring Metrics Details

Tencent Cloud KeeWiDB Instance Monitoring¶

Metric Name	Metric Description	Metric Explanation	Unit	Dimensions	Statistical Granularity
`KeeCpuUtil`	CPU Utilization	KeeWiDB Node CPU Utilization	%	`instanceid`	5s, 60s, 300s, 3600s, 86400s
Connections	Connection Count	TCP Connection Count to the Instance	Count	`instanceid`	5s, 60s, 300s, 3600s, 86400s
ConnectionsUtil	Connection Utilization	Actual TCP Connection Count and Maximum Connection Count Ratio	%	`instanceid`	5s, 60s, 300s, 3600s, 86400s
KeeCommands	Total Requests	QPS, Number of Commands Executed per Second	Times/sec	`instanceid`	5s, 60s, 300s, 3600s, 86400s
KeeCmdRead	Read Requests	Number of Read Commands Executed per Second	Times/sec	`instanceid`	5s, 60s, 300s, 3600s, 86400s
KeeCmdWrite	Write Requests	Number of Write Commands Executed per Second	Times/sec	`instanceid`	5s, 60s, 300s, 3600s, 86400s
KeeCmdOtherKee	Other Requests	Number of Commands Executed Other than Read/Write Commands	Count	`instanceid`, `keewidbnodeid`	5s, 60s, 300s, 3600s, 86400s
KeeCmdSlow	Slow Queries	Number of Commands with Execution Latency Greater than `slowlog` - log - slower - than Configuration	Count	`instanceid`	5s, 60s, 300s, 3600s, 86400s
CmdErr	Execution Errors	Number of Proxy Command Execution Errors per Second, e.g., Command Not Found, Parameter Errors, etc.	Times/sec	`instanceid`	5s, 60s, 300s, 3600s, 86400s
`KeeKeyspaceHitUtil`	Cache Hit Rate	The ratio of data requests found in the cache. Cache Hit Rate = Cache Hits / Total Requests	%	`instanceid`	5s, 60s, 300s, 3600s, 86400s
KeeKeys	Total Key Count	Total Key Count Stored in the Instance (Primary Keys)	Count	`instanceid`	5s, 60s, 300s, 3600s, 86400s
KeeExpireKeys	Expired Key Count	Number of Keys Evicted within the Time Window, Corresponding to expired_keys in the info Command	Count/sec	`instanceid`	5s, 60s, 300s, 3600s, 86400s
KeeDiskUsed	Disk Usage	Disk Capacity Used	MB	`instanceid`	5s, 60s, 300s, 3600s, 86400s
KeeDiskUtil	Disk Utilization	Ratio of Disk Capacity Used to Maximum Capacity	%	`instanceid`	5s, 60s, 300s, 3600s, 86400s
KeeDiskIops	Disk IOPS Usage	Number of Input/Output Operations per Second.	Times/sec	`instanceid`	5s, 60s, 300s, 3600s, 86400s

Object¶

Collected Tencent Cloud KeeWiDB Object Data Structure, 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}"
  }
}

Partial Parameter Descriptions

Field	Type	Description
`Status`	str	Current Instance Status. 0: To be initialized. 1: Instance in process. 2: Instance running. -2: Instance isolated. -3: Instance to be deleted.
`ProductType`	str	Product Type. standalone: Standard Edition. cluster: Cluster Edition.
`BillingMode`	str	Billing Mode. 0: Pay-as-you-go. 1: Subscription.
`ProjectId`	str	Project ID
`NodeSet`	str	Detailed Node Information of the Instance. Note: This field may return null, indicating no valid value.

Note: Fields in tags, fields may change with subsequent updates Tip 1: tags.name value is the Instance ID, used as the unique identifier. Tip 2: fields.message is the JSON serialized string.