Ravindra BagaleCourses & study guides मराठी Track your progress

Ravi Sir's Cards › AWS

Throttle metrics

This revision card explains Throttle metrics. Users see 400s before ops notices capacity or hot keys. It describes watch ThrottledRequests, ConsumedRead/WriteCapacityUnits, SuccessfulRequestLatency. The how-to section notes alarm on throttle , then check hot partition , then raise WCU or redesign keys. An example on the card is ops runbooks open CloudWatch before guessing the SDK.

Throttle metrics Users see 400s before ops notices capacity or hot keys. Watch ThrottledRequests, ConsumedRead/WriteCapacityUnits, SuccessfulRequestLatency. Alarm on throttle → check hot partition → raise WCU or redesign keys. Ops runbooks open CloudWatch before guessing the SDK.
Throttle metrics · Download PNG
Read card text

What this card says

Why do we need it?

Users see 400s before ops notices capacity or hot keys.

What is it?

Watch ThrottledRequests, ConsumedRead/WriteCapacityUnits, SuccessfulRequestLatency.

ThrottledRequests

How to do it

Alarm on throttle → check hot partition → raise WCU or redesign keys.

Example

Ops runbooks open CloudWatch before guessing the SDK.

See all AWS revision cards