Tencent Cloud KeeWiDB¶

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

Configuration¶

Install Func¶

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

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

Install Script¶

Note: Please prepare the Tencent Cloud AK with the required permissions 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: 「TrueWatch Integration (Tencent Cloud-KeeWiDB Collection)」(ID: integration_tencentcloud_keewidb).

Click 【Install】, then enter the corresponding parameters: Tencent Cloud AK, Tencent Cloud account name.

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

In addition, you can see the corresponding automatic trigger configuration in 「Manage / Automatic Trigger Configuration」. Click 【Execute】 to execute it immediately once, 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 automatic trigger configuration, and you can also check the corresponding task records and logs to see if there are any exceptions.
In TrueWatch, check if there is asset information in 「Infrastructure / Custom」.
In TrueWatch, 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 Monitoring Metrics Details

Tencent Cloud KeeWiDB Instance Monitoring¶

Metric Name	Metric Chinese Name	Metric Description	Unit	Dimensions	Statistical Granularity
`KeeCpuUtil`	CPU Utilization	KeeWiDB Node CPU Utilization	%	`instanceid`	5s, 60s, 300s, 3600s, 86400s
Connections	Connection Count	Number of TCP connections to the instance	Count	`instanceid`	5s, 60s, 300s, 3600s, 86400s
ConnectionsUtil	Connection Utilization	Ratio of actual TCP connections to maximum connections	%	`instanceid`	5s, 60s, 300s, 3600s, 86400s
KeeCommands	Total Requests	QPS, number of commands executed per second	Count/sec	`instanceid`	5s, 60s, 300s, 3600s, 86400s
KeeCmdRead	Read Requests	Number of read commands executed per second	Count/sec	`instanceid`	5s, 60s, 300s, 3600s, 86400s
KeeCmdWrite	Write Requests	Number of write commands executed per second	Count/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, such as command not found, parameter errors, etc.	Count/sec	`instanceid`	5s, 60s, 300s, 3600s, 86400s
`KeeKeyspaceHitUtil`	Cache Hit Rate	The ratio of requests that are found in the cache to the total number of requests. Cache Hit Rate = Cache Hits / Total Requests	%	`instanceid`	5s, 60s, 300s, 3600s, 86400s
KeeKeys	Total Key Count	Total number of keys stored in the instance (first-level keys)	Count	`instanceid`	5s, 60s, 300s, 3600s, 86400s
KeeExpireKeys	Expired Key Count	Number of keys evicted within the time window, corresponding to the expired_keys output by the info command	Count/sec	`instanceid`	5s, 60s, 300s, 3600s, 86400s
KeeDiskUsed	Disk Usage	Disk capacity already used	MB	`instanceid`	5s, 60s, 300s, 3600s, 86400s
KeeDiskUtil	Disk Utilization	Ratio of disk capacity already used to maximum capacity	%	`instanceid`	5s, 60s, 300s, 3600s, 86400s
KeeDiskIops	Disk IOPS Usage	Number of input/output operations per second on the disk.	Count/sec	`instanceid`	5s, 60s, 300s, 3600s, 86400s

Objects¶

The collected Tencent Cloud KeeWiDB object data structure can be seen 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 are as follows

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 information of instance nodes. 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.