AWS DocumentDB¶
The displayed metrics of AWS DocumentDB include read and write throughput, query latency, and scalability.
Configuration¶
Install Func¶
It is recommended to activate the Guance integration - extension - DataFlux Func (Automata): all prerequisites are automatically installed, please continue with the script installation.
For self-deploying Func, refer to Self-deploying Func
Install Script¶
Note: Please prepare the Amazon AK that meets the requirements in advance (for simplicity, you can directly grant global read-only permissions
ReadOnlyAccess
)
Automata Activation Script¶
- Log in to the Guance console
- Click the 【Integration】 menu and select 【Cloud Account Management】
- Click 【Add Cloud Account】, select 【AWS】, and fill in the required information on the interface. If the cloud account information has been configured before, ignore this step.
- Click 【Test】, and after the test is successful, click 【Save】. If the test fails, please check if the relevant configuration information is correct and test again.
- Click 【Cloud Account Management】, and you can see the added cloud account in the list. Click the corresponding cloud account to enter the details page.
- Click the 【Integration】 button on the cloud account details page, find
AWS DocumentDB
under theNot Installed
list, and click the 【Install】 button to pop up the installation interface for installation.
Manual Activation Script¶
-
Log in to the Func console, click 【Script Market】, enter the Guance script market, and search:
integration_aws_documentdb
-
Click 【Install】, then enter the corresponding parameters: AWS AK ID, AK Secret, and account name.
-
Click 【Deploy Startup Script】, the system will automatically create the
Startup
script set and automatically configure the corresponding startup scripts. -
After activation, you can see the corresponding automatic trigger configuration in 「Manage / Automatic Trigger Configuration」. Click 【Execute】 to execute it immediately 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 corresponding automatic trigger configuration, and you can also check the corresponding task records and logs to check for any abnormalities.
- In Guance, check if there is asset information in 「Infrastructure / Custom」.
- In Guance, check if there is corresponding monitoring data in 「Metrics」.
Metrics¶
After configuring Amazon CloudWatch, the default Measurement is as follows. More metrics can be collected through configuration. Amazon CloudWatch Metrics Details
Metric | Description |
---|---|
CPUUtilization |
The percentage of CPU utilized by the instance. |
FreeableMemory |
The amount of available random access memory in bytes. |
FreeLocalStorage |
This metric reports the amount of storage available for temporary tables and logs in each instance. This value depends on the instance class. You can increase the storage available to the instance by selecting a larger instance class for the instance. |
SwapUsage |
The amount of swap space used on the instance. |
DatabaseConnections |
The number of connections opened on the instance at one-minute frequency. |
DatabaseConnectionsMax |
The maximum number of database connections opened on the instance within one minute. |
DatabaseCursors |
The number of cursors opened on the instance at one-minute frequency. |
DatabaseCursorsMax |
The maximum number of cursors opened on the instance within one minute. |
DatabaseCursorsTimedOut |
The number of cursors that timed out within one minute. |
LowMemThrottleQueueDepth |
The queue depth of requests throttled due to insufficient available memory, at one-minute frequency. |
LowMemThrottleMaxQueueDepth |
The maximum queue depth of requests throttled due to insufficient available memory within one minute. |
LowMemNumOperationsThrottled |
The number of requests throttled due to insufficient available memory within one minute. |
ReadThroughput |
The average number of bytes read from disk per second. |
WriteThroughput |
The average number of bytes written to disk per second. |
ReadIOPS |
The average number of disk read I/O operations per second. Amazon DocumentDB reports read and write IOPS separately every minute. |
NetworkThroughput |
The network throughput received and sent to clients by each instance in the Amazon DocumentDB cluster, in bytes per second. This throughput does not include network traffic between instances in the cluster and the cluster volume. |
NetworkReceiveThroughput |
The network throughput received from clients by each instance in the cluster, in bytes per second. This throughput does not include network traffic between instances in the cluster and the cluster volume. |
NetworkTransmitThroughput |
The network throughput sent to clients by each instance in the cluster, in bytes per second. This throughput does not include network traffic between instances in the cluster and the cluster volume. |
WriteIOPS |
The average number of disk write I/O operations per second. When used at the cluster level, WriteIOPs will be evaluated on all instances in the cluster. Read and write IOPS are reported separately every minute. |
ReadLatency |
The average time taken per disk I/O operation. |
WriteLatency |
The average time taken per disk I/O operation in milliseconds. |
DBInstanceReplicaLag |
The total lag in milliseconds when replicating updates from the primary instance to the replica instance. |
OpcountersQuery |
The number of queries issued within one minute. |
OpcountersCommand |
The number of commands issued within one minute. |
OpcountersDelete |
The number of delete operations issued within one minute. |
OpcountersGetmore |
The number of get more operations issued within one minute. |
OpcountersInsert |
The number of insert operations issued within one minute. |
OpcountersUpdate |
The number of update operations issued within one minute. |
DocumentsDeleted |
The number of documents deleted within one minute. |
DocumentsInserted |
The number of documents inserted within one minute. |
DocumentsReturned |
The number of documents returned within one minute. |
DocumentsUpdated |
The number of documents updated within one minute. |
TTLDeletedDocuments |
The number of documents deleted by TTLMonitor within one minute. |
IndexBufferCacheHitRatio |
The percentage of index requests served by the cache. You may see a spike in this metric greater than 100% immediately after deleting an index, collection, or database. This will be automatically corrected after 60 seconds. This limitation will be fixed in a future patch update. |
BufferCacheHitRatio |
The percentage of requests served by the buffer cache. |
DiskQueueDepth |
The number of concurrent write requests to the distributed storage volume. |
EngineUptime |
The length of time the instance has been running in seconds. |
Object¶
The collected AWS DocumentDB object data structure can be seen in 「Infrastructure - Custom」
{
"measurement": "aws_documentdb",
"tags": {
"AvailabilityZone" : "cn-north-1a",
"CACertificateIdentifier" : "rds-ca-2019",
"DBClusterIdentifier" : "docdb-2023-06",
"DBInstanceArn" : "arn:aws-cn:rds:cn-north-1:",
"DBInstanceClass" : "db.t3.medium",
"DBInstanceIdentifier" : "docdb-2023-07",
"DBInstanceStatus" : "available",
"DbiResourceId" : "db-CKJQ",
"Engine" : "docdb",
"EngineVersion" : "3.6.0",
"KmsKeyId" : "arn:aws-cn:kms:cn-north-1:",
"cloud_provider" : "aws",
"name" : "docdb-2023-07"
},
"fields": {
"DBSubnetGroup": "{}",
"Endpoint": "{\"Address\": \".docdb.cn-north-1.amazonaws.com.cn\", \"HostedZoneId\": \"Z010911BG9\", \"Port\": 27017}",
"InstanceCreateTime": "2023-07-28T05:45:10.004000Z",
"PendingModifiedValues": "{}",
"PubliclyAccessible": "False",
"StatusInfos": "{}",
"VpcSecurityGroups": "[{\"Status\": \"active\", \"VpcSecurityGroupId\": \"sg-08895f59\"}]",
"message": "{instance json info}"
}
}
Note: The fields in
tags
andfields
may change with subsequent updates.