AWS DynamoDB¶

The displayed Metrics for AWS DynamoDB include throughput capacity units, latency, concurrent connections, and read/write throughput, etc. These Metrics reflect the performance and scalability of DynamoDB when handling large-scale data storage and accesses.

Configuration¶

Install Func¶

It is recommended to enable Guance integration - extension - hosted Func: all prerequisites are automatically installed. Please continue with the script installation.

If you deploy Func on your own, refer to Self-deployed Func

Installation Script¶

Note: Please prepare an Amazon AK that meets the requirements in advance (for simplicity, you can directly grant global read-only permission ReadOnlyAccess)

Hosted Edition Activation Script¶

Log in to the Guance console.
Click the 【Integration】 menu, select 【Cloud Account Management】.
Click 【Add Cloud Account】, choose 【AWS】, fill in the required information on the interface; if cloud account information has been configured before, skip this step.
Click 【Test】, after a successful test, click 【Save】; if the test fails, check whether the related configuration information is correct and retest.
In the 【Cloud Account Management】 list, you can see the added cloud accounts, click the corresponding cloud account, and enter the details page.
Click the 【Integration】 button on the cloud account details page. Under the Not Installed list, find AWS DynamoDB, click the 【Install】 button, and install it through the installation interface.

Manual Activation Script¶

Log in to the Func console, click 【Script Market】, enter the official script market, search:guance_aws_dynamodb
After clicking 【Install】, input the corresponding parameters: AWS AK ID, AK Secret, and account name.
Click 【Deploy Startup Script】, the system will automatically create a Startup script set and automatically configure the corresponding startup script.
After enabling, you can see the corresponding automatic trigger configuration in 「Management / Automatic Trigger Configuration」. Click 【Execute】, and you can execute immediately without waiting for the scheduled time. Wait for a moment, and you can view the execution task records and corresponding logs.

Verification¶

In 「Management / Automatic Trigger Configuration」, confirm whether the corresponding tasks have the corresponding automatic trigger configurations, and at the same time, you can check the corresponding task records and logs to see if there are any abnormalities.
In Guance, 「Infrastructure / Custom」, check if asset information exists.
In Guance, 「Metrics」, check if corresponding monitoring data exists.

Metrics¶

After configuring Amazon-CloudWatch, the default Measurement set is as follows. You can collect more Metrics through configuration. Amazon CloudWatch Metrics Details

ConditionalCheckFailedRequests¶

The number of failed attempts to perform conditional writes.

Metric Name	Description	Unit	Dimensions
ConditionalCheckFailedRequests_Average	Average number of failed requests	Count	TableName
ConditionalCheckFailedRequests_Maximum	Maximum value of failed requests	Count	TableName
ConditionalCheckFailedRequests_Minimum	Minimum value of failed requests	Count	TableName
ConditionalCheckFailedRequests_SampleCount	Number of failed requests	Count	TableName
ConditionalCheckFailedRequests_Sum	Total number of failed requests	Count	TableName

ConsumedReadCapacityUnits¶

The number of read capacity units consumed during a specified period, allowing you to track the use of provisioned throughput.

Metric Name	Description	Unit	Dimensions
ConsumedReadCapacityUnits_Average	Average read capacity consumed per request	Count	TableName
ConsumedReadCapacityUnits_Maximum	Maximum number of read capacity units consumed by any request to a table or index	Count	TableName
ConsumedReadCapacityUnits_Minimum	Minimum number of read capacity units consumed by any request to a table or index	Count	TableName
ConsumedReadCapacityUnits_SampleCount	Number of read requests to DynamoDB, even if no read capacity was consumed	Count	TableName
ConsumedReadCapacityUnits_Sum	Total number of read capacity units consumed	Count	TableName

ConsumedWriteCapacityUnits¶

The number of write capacity units consumed during a specified period, allowing you to track the use of provisioned throughput.

Metric Name	Description	Unit	Dimensions
ConsumedWriteCapacityUnits_Average	Average write capacity consumed per request	Count	TableName
ConsumedWriteCapacityUnits_Maximum	Maximum number of write capacity units consumed by any request to a table or index	Count	TableName
ConsumedWriteCapacityUnits_Minimum	Minimum number of write capacity units consumed by any request to a table or index	Count	TableName
ConsumedWriteCapacityUnits_SampleCount	Number of write requests to DynamoDB, even if no read capacity was consumed	Count	TableName
ConsumedWriteCapacityUnits_Sum	Total number of write capacity units consumed	Count	TableName

Objects¶

The collected AWS DynamoDB object data structure can be viewed from 「Infrastructure - Custom」.

{
  "measurement": "aws_dynamodb",
  "tags": {
      "RegionId"        : "cn-north-1",
      "TableArn"        : "arn:aws-cn:dynamodb:cn-north-1:",
      "TableId"         : "0ce8d4f9b35",
      "TableName"       : "eks-tflock",
      "TableStatus"     : "ACTIVE",
      "name"            : "eks-tflock"
  },
  "fields": {
    "AttributeDefinitions"  : "[{\"AttributeName\": \"LockID\", \"AttributeType\": \"S\"}]",
    "BillingModeSummary"    : "{}",
    "CreationDateTime"      : "2023-03-22T23:39:42.352000+08:00",
    "ItemCount"             : "1",
    "KeySchema"             : "[{\"AttributeName\": \"LockID\", \"KeyType\": \"HASH\"}]",
    "LocalSecondaryIndexes" : "{}",
    "TableSizeBytes"        : "96",
    "message"               : "{Instance JSON information}"
  }
}

Note: Fields in tags and fields may change with subsequent updates.

Tip 1: The value of tags.name is the instance ID, used as unique identification.

Tip 2: fields.message, fields.Endpoint are strings serialized in JSON.