Volcengine MongoDB Replica Set¶
Volcengine MongoDB Replica Set Metrics display, including CPU usage, memory usage, connection count, latency, OPS, etc..
Configuration¶
Install Func¶
It is recommended to enable TrueWatch Integration - Extensions - DataFlux Func (Automata): All prerequisites are automatically installed, please proceed with the script installation.
If you need to deploy Func manually, refer to Manual Deployment of Func
Install Script¶
Note: Please prepare the Volcengine AK in advance (for simplicity, you can directly grant the global read-only permission
ReadOnlyAccess
).
To synchronize the monitoring data of MongoDB cloud resources, we install the corresponding collection script: "TrueWatch Integration (Volcengine-MongoDB Collection)" (ID: integration_volcengine_mongodb_replica_set
).
After clicking [Install], enter the corresponding parameters: Volcengine AK, Volcengine account name.
Click [Deploy Startup Script], the system will automatically create the Startup
script set and configure the corresponding startup script.
After enabling, 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.
If you want to collect corresponding logs, you also need to enable the corresponding log collection script. If you want to collect bills, you need to enable the cloud bill collection script.
Verification¶
- In "Manage / Automatic Trigger Configuration", confirm whether the corresponding task has the corresponding automatic trigger configuration, and you can also check the corresponding task records and logs to check for any exceptions.
- In TrueWatch, check whether the asset information exists in "Infrastructure / Custom".
- In TrueWatch, check whether the corresponding monitoring data exists in "Metrics".
Metrics¶
After configuring Volcengine-MongoDB Replica Set monitoring, the default Measurement is as follows. You can collect more metrics through configuration Volcengine MongoDB Monitoring Metrics Details
MetricName |
Subnamespace |
Metric Name | MetricUnit | Dimension |
---|---|---|---|---|
AggregatedCpuUtil |
instance |
CPU Usage | Percent | ResourceID |
AggregatedMemUtil |
instance |
Memory Usage | Percent | ResourceID |
AggregatedTotalDiskUtil |
instance |
Total Disk Space Usage | Percent | ResourceID |
NetworkReceiveThroughput |
replica |
Network Input Rate | Bytes/Second(SI) | ResourceID,Node |
RunningConcurrentWriteRequest |
replica |
Current Write Concurrent Requests | Count | ResourceID,Node |
LogDiskUsage |
replica |
Log Disk Usage | Bytes(SI) | ResourceID,Node |
RunningConcurrentReadRequest |
replica |
Current Read Concurrent Requests | Count | ResourceID,Node |
CommandOperationPerSec |
replica |
COMMAND Operations Per Second | Count/Second | ResourceID,Node |
ReplicationDelay |
replica |
Primary-Secondary Delay | Second | ResourceID,Node |
CurrConn |
replica |
Current Connections | Count | ResourceID,Node |
TotalDiskUsage |
replica |
Total Disk Usage | Bytes(SI) | ResourceID,Node |
UpdateOperationPerSec |
replica |
UPDATE Operations Per Second | Count/Second | ResourceID,Node |
MaxDiskConfigured |
replica |
Maximum Available Disk Space Configured | Bytes(SI) | ResourceID,Node |
TimeOutCursor |
replica |
Cursor Timeouts | Count | ResourceID,Node |
NetworkTransmitThroughput |
replica |
Network Output Rate | Bytes/Second(SI) | ResourceID,Node |
GlobalWaitReadLockQueue |
replica |
Global Read Lock Wait Queue Length | Count | ResourceID,Node |
AvailConcurrentReadRequest |
replica |
Available Read Concurrent Requests | Count | ResourceID,Node |
DataDiskUsage |
replica |
Data Disk Usage | Bytes(SI) | ResourceID,Node |
ReadIntoCachePerSec |
replica |
Data Read Into Cache Per Second | Bytes/Second(SI) | ResourceID,Node |
TotalDiskUtil |
replica |
Total Disk Usage | Percent | ResourceID,Node |
GlobalWaitWriteLockQueue |
replica |
Global Write Lock Wait Queue Length | Count | ResourceID,Node |
TotalOpenCursor |
replica |
Total Open Cursors | Count | ResourceID,Node |
GetmoreOperationPerSec |
replica |
GETMORE Operations Per Second | Count/Second | ResourceID,Node |
MemUtil |
replica |
Memory Usage | Percent | ResourceID,Node |
GlobalWaitTotalLockQueue |
replica |
Global Lock Wait Queue Total Length | Count | ResourceID,Node |
CpuUtil |
replica |
CPU Usage | Percent | ResourceID,Node |
QueryOperationPerSec |
replica |
QUERY Operations Per Second | Count/Second | ResourceID,Node |
DeleteOperationPerSec |
replica |
DELETE Operations Per Second | Count/Second | ResourceID,Node |
AvailConcurrentWriteRequest |
replica |
Available Write Concurrent Requests | Count | ResourceID,Node |
InsertOperationPerSec |
replica |
INSERT Operations Per Second | Count/Second | ResourceID,Node |
WrittenFromCachePerSec |
replica |
Data Written From Cache Per Second | Bytes/Second(SI) | ResourceID,Node |
NetworkRequestPerSec |
replica |
Network Requests Processed Per Second | Count/Second | ResourceID,Node |
SlowOpCount |
replica |
Slow Query Count | Count | ResourceID,Node |
OplogAvailTime |
replica |
Oplog Available Time | Second | ResourceID,Node |
Object¶
The collected Volcengine MongoDB object data structure can be seen in "Infrastructure-Custom".
{
"category": "custom_object",
"fields": {
"NodeSpec": "rds.mysql.d1.n.1c1g",
"TimeZone": "UTC +08:00",
...
},
"measurement": "volcengine_mongodb_replica_set",
"tags": {
"AllowListVersion": "initial",
"DBEngineVersion": "MongoDB_5_7",
"InstanceId": "mysql-xxx",
"InstanceName": "mysql-xxx",
"InstanceStatus": "Running",
"InstanceType": "DoubleNode",
"LowerCaseTableNames": "1",
"NodeNumber": "2",
"ProjectName": "default",
"RegionId": "cn-beijing",
"StorageSpace": "20",
"StorageType": "LocalSSD",
"SubnetId": "subnet-xxx",
"VpcId": "vpc-xxx",
"ZoneId": "cn-beijing-a",
"name": "mysql-xxx"
}
}