AWS DynamoDB

Note: Learn about the other supported AWS services with our AWS documentation.

Metrics collection

Configuration data

  • Table Arn
  • Table Name
  • Table Status
  • Table Item Count
  • Table Created At
  • Table Size (bytes)
  • Table Stream Arn
  • Table Stream Label
  • Grouping zone (region)

Performance metrics

Name
Consumed read capacity
Provisioned read capacity
Consumed write capacity
Provisioned write capacity
Throttled read requests (Get, Scan, Query, Batch Get)
Throttled write requests (Put, Update, Delete, Batch Write)
TTL Deleted Items
Conditional check failed
User errors
System errors read (Get, Scan, Query,Batch get)
System errors write (Put, Update, Delete, Batch write)
Returned query item count (Minimum, Maximum, Average, Sum)
Returned scan item count (Minimum, Maximum, Average, Sum)
Batch get latency (Minimum, Maximum, Average, Sum, Request count)
Batch write latency (Minimum, Maximum, Average, Sum, Request count)
Delete latency (Minimum, Maximum, Average, Sum, Request count)
Get latency (Minimum, Maximum, Average, Sum, Request count)
Put latency (Minimum, Maximum, Average, Sum, Request count)
Query latency (Minimum, Maximum, Average, Sum, Request count)
Scan latency (Minimum, Maximum, Average, Sum, Request count)

| Update latency (Minimum, Maximum, Average, Sum, Request count)

For more information refer to Amazon DynamoDB Metrics and Dimensions.

Health Signatures

For each sensor, there is a curated knowledgebase of health signatures that are evaluated continuously against the incoming metrics and are used to raise issues or incidents depending on user impact.

Built-in events trigger issues or incidents based on failing health signatures on entities, and custom events trigger issues or incidents based on the thresholds of an individual metric of any given entity.

For information about built-events for the AWS DynamoDB sensor, see the Built-in events reference.

Required Permissions

  • cloudwatch:GetMetricStatistics
  • cloudwatch:GetMetricData
  • dynamodb:ListTables
  • dynamodb:DescribeTable
  • dynamodb:ListTagsOfResource

Configuration

Beanstalk instances are refreshed every 5 minutes. Due to an asynchronous nature of detection instance metrics can be late. This delay depends on the specified poll rate (cloudwatch_period) and by default it is not longer than a minute before they appear on the dashboard. Metrics for DynamoDB are pulled every 5 minutes, this can be changed via agent configuration in /opt/instana/agent/etc/instana/configuration.yml:

com.instana.plugin.aws.dynamodb:
  cloudwatch_period: 300

To disable monitoring of DynamoDB instances use the following configuration:

com.instana.plugin.aws.dynamodb:
  enabled: false

Monitoring multiple AWS accounts

Refer to the Monitoring multiple AWS accounts documentation to set up monitoring of multiple AWS accounts with one AWS agent in the same region.

To override which profiles should be used to monitor DynamoDB, use the following configuration:

com.instana.plugin.aws.dynamodb:
  profile_names:
    - 'profile2'
    - 'profile3'

Note: Defining profiles on service level will override global AWS configuration.

Filtering

Multiple tags can be defined, separated by a comma. Tags should be provided as a key-value pair separated by a : character. In order to make configuration easier, it is possible to define which tags you want to include in discovery or exclude from discovery. In case of tags defined in both lists (include and exclude), exclude list has higher priority. If there is no need for services filtering, the configuration should not be defined. It is not mandatory to define all values in order to enable filtering.

Users are able to specify how often sensors will poll the AWS tagged resources using the tagged-services-poll-rate configuration property (default 300 seconds).

Note: Tags are only available in conjunction with the AWS Agent.

To define how often sensors will poll the tagged resources use following configuration:

com.instana.plugin.aws:
  tagged-services-poll-rate: 60 #default 300

To include services by tags into discovery use following configuration:

com.instana.plugin.aws.dynamodb:
  include_tags: # Comma separated list of tags in key:value format (e.g. env:prod,env:staging)

To exclude services by tags from discovery use following configuration:

com.instana.plugin.aws.dynamodb:
  exclude_tags: # Comma separated list of tags in key:value format (e.g. env:dev,env:test)

Poll Rate

To define how often sensors will poll the tagged resources use following configuration:

com.instana.plugin.aws:
  tagged-services-poll-rate: 60 #default 300