Alibaba Cloud¶
Alibaba Cloud MongoDB replica set Metrics display, including CPU usage, memory usage, disk usage, data occupying disk space, log occupying disk space, statements executed per second, request count, connection count, network traffic, replication delay, QPS, etc.
Alibaba Cloud MongoDB sharding cluster Metrics display, including CPU usage, memory usage, disk usage, data occupying disk space, log occupying disk space, statements executed per second, request count, connection count, network traffic, replication delay, QPS, etc.
Alibaba Cloud MongoDB single-node instance Metrics display, including CPU usage, memory usage, disk usage, data occupying disk space, statements executed per second, request count, connection count, network traffic, QPS, etc.
Configuration¶
Install Func¶
It is recommended to activate the Guance integration - extension - hosted Func.
If you deploy Func yourself, refer to Self-deployed Func
Activate Script¶
Tip: Please prepare an Alibaba Cloud AK in advance that meets the requirements (for simplicity, you can directly grant global read-only permission
ReadOnlyAccess
).
Hosted Activation Script¶
- Log in to the Guance console.
- Click on the [Integration] menu and select [Cloud Account Management].
- Click [Add Cloud Account], select [Alibaba Cloud], and fill in the required information on the interface; if you have configured cloud account information before, ignore this step.
- Click [Test]. After a successful test, click [Save]. If the test fails, check whether the relevant configuration information is correct and retest.
- In the [Cloud Account Management] list, you can see the added cloud account. Click the corresponding cloud account to enter the details page.
- Click the [Integrate] button on the cloud account details page. Under the
Not Installed
list, findAlibaba Cloud MongoDB
, click the [Install] button, and install it by following the installation interface.
Manual Activation Script¶
-
Log in to the Func console, click [Script Market], go to the official script market, and search for
guance_aliyun_mongodb
. -
After clicking [Install], input the corresponding parameters: Alibaba Cloud AK ID, AK Secret, and account name.
-
Click [Deploy Startup Script], and the system will automatically create a
Startup
Measurement set and configure the corresponding startup script automatically. -
After activation, you can see the corresponding automatic trigger configuration under "Management / Automatic Trigger Configuration". Click [Execute] to run it immediately without waiting for the scheduled time. After a short wait, you can view the execution task records and corresponding logs.
We default collect some configurations, see Metrics section for details.
Configure Custom Cloud Object Metrics
Verification¶
- In "Management / Automatic Trigger Configuration", confirm whether the corresponding task has the corresponding automatic trigger configuration. You can also view the corresponding task records and logs to check for any abnormalities.
- In Guance, "Infrastructure / Custom", check if there is asset information.
- In Guance, "Metrics", check if there are corresponding monitoring data.
Metrics¶
After configuring Alibaba Cloud - Cloud Monitoring, the default collected Metrics are as follows, and more Metrics can be collected through configuration. For more Metrics, please refer to: Alibaba Cloud Cloud Monitoring Metrics Details
Cloud Database MongoDB Edition - Replica Set¶
Metric Id | MetricCategory | Metric Name | Dimensions | Statistics | Unit | Min Periods |
---|---|---|---|---|---|---|
CPUUtilization |
mongodb_replicaset |
CPU Usage | userId,instanceId,role | Average,Minimum,Maximum | % | 60 s |
ConnectionAmount |
mongodb_replicaset |
Connection Volume | userId,instanceId,role | Average,Minimum,Maximum | Count | 60 s |
ConnectionUtilization |
mongodb_replicaset |
Connection Usage | userId,instanceId,role | Average,Minimum,Maximum | % | 60 s |
DataDiskAmount |
mongodb_replicaset |
Data Occupying Disk Space | userId,instanceId,role | Average,Minimum,Maximum | bytes | 60 s |
DiskUtilization |
mongodb_replicaset |
Disk Usage | userId,instanceId,role | Average,Minimum,Maximum | % | 60 s |
IOPSUtilization |
mongodb_replicaset |
IOPS Usage | userId,instanceId,role | Average,Minimum,Maximum | % | 60 s |
InstanceDiskAmount |
mongodb_replicaset |
Instance Occupying Disk Space | userId,instanceId,role | Average,Minimum,Maximum | bytes | 60 s |
IntranetIn |
mongodb_replicaset |
Network Inbound Traffic | userId,instanceId,role | Average,Minimum,Maximum | bytes | 60 s |
IntranetOut |
mongodb_replicaset |
Network Outbound Traffic | userId,instanceId,role | Average,Minimum,Maximum | bytes | 60 s |
LogDiskAmount |
mongodb_replicaset |
Logs Occupying Disk Space | userId,instanceId,role | Average,Minimum,Maximum | bytes | 60 s |
MemoryUtilization |
mongodb_replicaset |
Memory Usage | userId,instanceId,role | Average,Minimum,Maximum | % | 60 s |
NumberRequests |
mongodb_replicaset |
Request Count | userId,instanceId,role | Average,Minimum,Maximum | Count | 60 s |
OpCommand |
mongodb_replicaset |
Command Operation Count | userId,instanceId,role | Average,Minimum,Maximum | Frequency | 60 s |
OpDelete |
mongodb_replicaset |
Delete Operation Count | userId,instanceId,role | Average,Minimum,Maximum | Frequency | 60 s |
OpGetmore |
mongodb_replicaset |
Getmore Operation Count | userId,instanceId,role | Average,Minimum,Maximum | Frequency | 60 s |
OpInsert |
mongodb_replicaset |
Insert Operation Count | userId,instanceId,role | Average,Minimum,Maximum | Count | 60 s |
OpQuery |
mongodb_replicaset |
Query Operation Count | userId,instanceId,role | Average,Minimum,Maximum | Frequency | 60 s |
OpUpdate |
mongodb_replicaset |
Update Operation Count | userId,instanceId,role | Average,Minimum,Maximum | Frequency | 60 s |
QPS |
mongodb_replicaset |
Average SQL Queries Per Second | userId,instanceId,role | Average,Minimum,Maximum | Count | 60 s |
ReplicationLag |
mongodb_replicaset |
Replication Delay | userId,instanceId,role | Average,Maximum,Minimum,cms_null | seconds | 60 s |
Cloud Database MongoDB Edition - Sharding Cluster¶
Metric Id | MetricCategory | Metric Name | Dimensions | Statistics | Unit | Min Periods |
---|---|---|---|---|---|---|
ShardingCPUUtilization |
mongodb_sharding |
CPU Usage | userId,instanceId,subinstanceId,role |
Average,Minimum,Maximum | % | 60 s |
ShardingConnectionAmount |
mongodb_sharding |
Connection Volume | userId,instanceId,subinstanceId,role |
Average,Minimum,Maximum | Count | 60 s |
ShardingConnectionUtilization |
mongodb_sharding |
Connection Usage | userId,instanceId,subinstanceId,role |
Average,Minimum,Maximum | % | 60 s |
ShardingDataDiskAmount |
mongodb_sharding |
Data Occupying Disk Space | userId,instanceId,subinstanceId,role |
Average,Minimum,Maximum | Bytes | 60 s |
ShardingDataDiskAmountOriginal |
mongodb_sharding |
ShardingDataDiskAmountOriginal | userId,instanceId,subinstanceId,role |
Average,Minimum,Maximum | - | 60 s |
ShardingDiskUtilization |
mongodb_sharding |
Disk Usage | userId,instanceId,subinstanceId,role |
Average,Minimum,Maximum | % | 60 s |
ShardingIOPSUtilization |
mongodb_sharding |
IOPS Usage | userId,instanceId,subinstanceId,role |
Average,Minimum,Maximum | % | 60 s |
ShardingInstanceDiskAmount |
mongodb_sharding |
Occupying Disk Space | userId,instanceId,subinstanceId,role |
Average,Minimum,Maximum | Bytes | 60 s |
ShardingIntranetIn |
mongodb_sharding |
Network Inbound Traffic | userId,instanceId,subinstanceId,role |
Average | Bytes | 60 s |
ShardingIntranetOut |
mongodb_sharding |
Network Outbound Traffic | userId,instanceId,subinstanceId,role |
Average | Bytes | 60 s |
ShardingLogDiskAmount |
mongodb_sharding |
Logs Occupying Disk Capacity | userId,instanceId,subinstanceId,role |
Average,Minimum,Maximum | Bytes | 60 s |
ShardingMemoryUtilization |
mongodb_sharding |
Memory Usage | userId,instanceId,subinstanceId,role |
Average,Minimum,Maximum | % | 60 s |
ShardingNumberRequests |
mongodb_sharding |
Request Count | userId,instanceId,subinstanceId,role |
Average | Count | 60 s |
ShardingOpCommand |
mongodb_sharding |
Command Operation Count | userId,instanceId,subinstanceId,role |
Average,Minimum,Maximum | Count | 60 s |
ShardingOpDelete |
mongodb_sharding |
Delete Operation Count | userId,instanceId,subinstanceId,role |
Average,Minimum,Maximum | Count | 60 s |
ShardingOpGetmore |
mongodb_sharding |
Getmore Operation Count | userId,instanceId,subinstanceId,role |
Average,Minimum,Maximum | Count | 60 s |
ShardingOpInsert |
mongodb_sharding |
Insert Operation Count | userId,instanceId,subinstanceId,role |
Average,Minimum,Maximum | Count | 60 s |
ShardingOpQuery |
mongodb_sharding |
Query Operation Count | userId,instanceId,subinstanceId,role |
Average,Minimum,Maximum | Count | 60 s |
Cloud Database MongoDB Edition - Single Node Instance¶
Metric Id | MetricCategory | Metric Name | Dimensions | Statistics | Unit | Min Periods |
---|---|---|---|---|---|---|
SingleNodeCPUUtilization |
mongodb_singlenode |
CPU Usage | userId,instanceId | Average,Minimum,Maximum | % | 60 s |
SingleNodeConnectionAmount |
mongodb_singlenode |
Connection Volume | userId,instanceId | Average,Minimum,Maximum | Count | 60 s |
SingleNodeConnectionUtilization |
mongodb_singlenode |
Connection Usage | userId,instanceId | Average,Minimum,Maximum | % | 60 s |
SingleNodeDataDiskAmount |
mongodb_singlenode |
Data Occupying Disk Space | userId,instanceId | Average,Minimum,Maximum | bytes | 60 s |
SingleNodeDiskUtilization |
mongodb_singlenode |
Disk Usage | userId,instanceId | Average,Minimum,Maximum | % | 60 s |
SingleNodeIntranetIn |
mongodb_singlenode |
Network Inbound Traffic | userId,instanceId | Average,Minimum,Maximum | bytes | 60 s |
SingleNodeIntranetOut |
mongodb_singlenode |
Network Outbound Traffic | userId,instanceId | Average,Minimum,Maximum | bytes | 60 s |
SingleNodeMemoryUtilization |
mongodb_singlenode |
Memory Usage | userId,instanceId | Average,Minimum,Maximum | % | 60 s |
SingleNodeNumberRequests |
mongodb_singlenode |
Request Count | userId,instanceId | Average,Minimum,Maximum | Count | 60 s |
SingleNodeOpCommand |
mongodb_singlenode |
Command Operation Count | userId,instanceId | Average,Minimum,Maximum | Count | 60 s |
SingleNodeOpDelete |
mongodb_singlenode |
Delete Operation Count | userId,instanceId | Average,Minimum,Maximum | Count | 60 s |
SingleNodeOpGetmore |
mongodb_singlenode |
Getmore Operation Count | userId,instanceId | Average,Minimum,Maximum | Count | 60 s |
SingleNodeOpInsert |
mongodb_singlenode |
Insert Operation Count | userId,instanceId | Average,Minimum,Maximum | Count | 60 s |
SingleNodeOpQuery |
mongodb_singlenode |
Query Operation Count | userId,instanceId | Average,Minimum,Maximum | Count | 60 s |
SingleNodeOpUpdate |
mongodb_singlenode |
Update Operation Count | userId,instanceId | Average,Minimum,Maximum | Count | 60 s |
SingleNodeQPS |
mongodb_singlenode |
QPS | userId,instanceId | Average,Minimum,Maximum | Count | 60 s |
Objects¶
Collected Alibaba Cloud MongoDB object data structure, which can be viewed from "Infrastructure - Custom".
{
"measurement": "aliyun_mongodb",
"tags": {
"name" : "dds-bpxxxxxxxx",
"DBInstanceType" : "replicate",
"ChargeType" : "PrePaid",
"Engine" : "MongoDB",
"DBInstanceClass" : "dds.xxxxxxxx",
"DBInstanceId" : "dds-bpxxxxxxx",
"ZoneId" : "cn-hangzhou",
"RegionId" : "cn-hangzhou-h",
"VPCId" : "vpc-bpxxxxxxxx",
"EngineVersion" : "4.2",
"CurrentKernelVersion" : "mongodb_20210204_4.0.14",
"StorageEngine" : "WiredTiger",
"DBInstanceDescription": "Business System",
"LockMode" : "Unlock",
},
"fields": {
"ExpireTime" : "2020-11-18T08:47:11Z",
"DBInstanceStorage": "20",
"ReplicaSets" : "{Connection Address JSON Data}",
"message" : "{Instance JSON Data}",
}
}
Logs¶
Slow Query Logs¶
Prerequisites¶
Tip: The code execution of this script depends on mongodb instance object collection. If you have not configured the custom object collection for mongodb, the slow log script will not be able to collect slow log data.
Install Slow Query Collection Script¶
Based on the previous steps, you need to install another script corresponding to MongoDB Slow Query Collection.
In the "Script Market - Official Script Market", go to "Details" and click to install the corresponding script package:
- "Guance Integration (Alibaba Cloud - MongoDB Slow Query Log Collection)" (ID:
guance_aliyun_mongodb
)
After data synchronization is normal, you can view the data in the "Logs" section of Guance.
An example of the reported data is as follows:
{
"measurement": "aliyun_mongodb_slowlog",
"tags": {
"name" : "dds-bpxxxxxxxx",
"DBInstanceType" : "replicate",
"ChargeType" : "PrePaid",
"Engine" : "MongoDB",
"DBInstanceClass" : "dds.xxxxxxxx",
"DBInstanceId" : "dds-bpxxxxxxx",
"ZoneId" : "cn-hangzhou",
"RegionId" : "cn-hangzhou-h",
"VPCId" : "vpc-bpxxxxxxxx",
"EngineVersion" : "4.2",
"CurrentKernelVersion" : "mongodb_20210204_4.0.14",
"StorageEngine" : "WiredTiger",
"DBInstanceDescription": "Business System",
"DBName" : "local",
"AccountName" : "Alibaba Cloud Account for Script Development",
"HostAddress" : "11.xxx.xxx.xx",
"TableName" : "oplog",
},
"fields": {
"SQLText" : "{SQL Statement}",
"ExecutionStartTime": "1",
"QueryTimes" : "1",
"ReturnRowCounts" : "1",
"KeysExamined" : "1",
"DocsExamined" : "1",
}
}
Descriptions of some parameters are as follows:
Field | Type | Description |
---|---|---|
QueryTimes |
Int | Execution duration, unit in milliseconds |
ExecutionStartTime |
Str | Execution start time, UTC time |
Note: Fields in
tags
,fields
may change with subsequent updates.Tip:
fields.message
is a string after JSON serialization.