This repository was archived by the owner on Dec 1, 2022. It is now read-only.
Add throttle metrics to describeTableConsumedCapacityAsync #29
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
From Amazon: "It is possible to have short spikes in consumed [READ/WRITE] capacity which do not show up [because] it is an average. So be careful when adjusting table [READ/WRITE] capacity to pay attention to the Throttled [READ/WRITE] Requests..."
Had a use-case for this type of functionality in my production system. Figured it would be useful for others and wanted to give back. Thanks for the awesome package!